Weirdness with fargo.io DNS lookups

Open
#29 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Domain
networking

Research direction

Start by rerunning the reported dig @8.8.8.8 fargo.io query and recording the returned addresses, TTLs, and any NXDOMAIN responses. Trace the authoritative DNS path for fargo.io and compare results over time; the issue is done when the intermittent response behavior is explained and any needed DNS correction is identified.

Written by the indexing model from the issue text.

Description

I had trouble viewing scripting.com this morning, and tracked down a few problems - one with my DSL ISP, but perhaps one with your DNS server.

I used dig @8.8.8.8 fargo.io to query the address for fargo.io from Google's DNS server, and get a variety of IP addresses:
52.216.130.234
52.216.131.82
52.216.97.18
54.231.41.17
... etc...

When it works, all the responses seem to have a TTL of 5 seconds or lower. This also seems odd, unless there's some kind of load sharing (maybe there is...)

And sometimes I get a No Such Domain (NXDOMAIN), like this example from around 10:30am this morning:

bash-3.2$ dig @8.8.8.8 fargo.io

; <<>> DiG 9.8.3-P1 <<>> @8.8.8.8 fargo.io
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 12631
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0

;; QUESTION SECTION:
;fargo.io.			IN	A

;; AUTHORITY SECTION:
io.			618	IN	SOA	a0.nic.io. noc.afilias-nst.info. 1497256201 10800 3600 2764800 900

;; Query time: 37 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Sep 20 10:32:36 2017
;; MSG SIZE  rcvd: 89

I'm OK for now, but I always work on the motto, "We promise not to fix it if we don't know it's broke..." :-)

Dominant language
HTML
Stars
134
Forks
10
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from scripting/Scripting-News

All issues in scripting/Scripting-News

Similar issues

More Networking issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.