SERVFAIL on EZE PoP but not on EWR


#1

Been trying to query calcularsueldo.com.ar and it’s failing only from my local PoP (but not when hitting it from a VM in NYC).

$ dig calcularsueldo.com.ar @1.1.1.1

; <<>> DiG 9.10.6 <<>> calcularsueldo.com.ar @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 21103
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1452
;; QUESTION SECTION:
;calcularsueldo.com.ar.		IN	A

;; Query time: 2206 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Wed Jan 02 14:25:38 -03 2019
;; MSG SIZE  rcvd: 50

$ dig calcularsueldo.com.ar @1.0.0.1

; <<>> DiG 9.10.6 <<>> calcularsueldo.com.ar @1.0.0.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 32036
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1452
;; QUESTION SECTION:
;calcularsueldo.com.ar.		IN	A

;; Query time: 4205 msec
;; SERVER: 1.0.0.1#53(1.0.0.1)
;; WHEN: Wed Jan 02 14:28:50 -03 2019
;; MSG SIZE  rcvd: 50

$ dig calcularsueldo.com.ar @8.8.8.8

; <<>> DiG 9.10.6 <<>> calcularsueldo.com.ar @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 14404
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;calcularsueldo.com.ar.		IN	A

;; ANSWER SECTION:
calcularsueldo.com.ar.	9070	IN	A	192.169.158.12

;; Query time: 27 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Jan 02 14:28:55 -03 2019
;; MSG SIZE  rcvd: 66

$ dig +short CHAOS TXT id.server @1.1.1.1
"EZE"

From my VM:

$ dig calcularsueldo.com.ar @1.1.1.1

; <<>> DiG 9.9.5-3ubuntu0.14-Ubuntu <<>> calcularsueldo.com.ar @1.1.1.1
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 52637
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1452
;; QUESTION SECTION:
;calcularsueldo.com.ar.		IN	A

;; ANSWER SECTION:
calcularsueldo.com.ar.	10623	IN	A	192.169.158.12

;; Query time: 3 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Wed Jan 02 14:06:32 ART 2019
;; MSG SIZE  rcvd: 66

$ dig +short CHAOS TXT id.server @1.1.1.1
"EWR"

#2

It appears as if the domain’s nameservers are not responsive.


#3

It’s working now, so I guess we can just /resolv it :stuck_out_tongue:


#4

The nameservers still do not respond.


#5

Yeah, I saw, the hostnames don’t but the IPs the NS records point to do, domain is resolving fine for me now. If they have a problem beyond that, it’s up to them


#6

If the hostnames dont work, the IP wont either.

That domain is currently configured with ns1.infokioscos.com.ar and ns2.infokioscos.com.ar, which have the addresses 198.154.246.123 and 198.1.64.34 respectively and neither responds.

If something is currently resolving it might be because of some cache, but that domain is definitely not properly configured.


#7

nserver: ns2.infokioscos.com.ar (192.169.159.7/32)
nserver: ns1.infokioscos.com.ar (192.169.158.12/32)

^ From whois data, those respond and are usually the ones used by DNS.

Again, works for me, if they have an issue or misconfiguration on their end, it’s on them to fix it. I had just opened this thread to check why it wasn’t resolving from EZE PoP (which is, and the TTL correlates with the time it started working again)


#8

Dont know where you got those addresses but both hostnames resolves to different IPs, the one mentioned earlier.

It is good if it works for you right now, but I’d expect it to stop again considering the nameserver issues. Just so that you are not surprised.


#9

In all honesty, don’t know how is it working right now. SOA doesn’t show recent updates