Community discussions

MUM Europe 2020
 
User avatar
janisk
MikroTik Support
MikroTik Support
Topic Author
Posts: 6283
Joined: Tue Feb 14, 2006 9:46 am
Location: Riga, Latvia

problems resolving IP Cloud addresses

Tue Jun 12, 2018 2:46 pm

On 12th of June surfaced some problems with nameservers as 3-month-old entries started to propagate through the global DNS servers. If you try to resolve ns1.kissthenet.net and ns2.kissthenet.net and as a result, you get 91.188.51.139 or 81.198.87.240 these are old addresses and get wrong IP address while trying to resolve your ns.mynetname.net address.

Some big DNS servers like 8.8.8.8; 8.8.4.4; 1.1.1.1 already return normal records so we firewalled off old NS servers.

If you are in control of DNS cache - we suggest to flush the cache and check if correct entries are retrieved (159.148.147.201 and 159.148.172.251) as ns1 and ns1 for mynetname.net zone.
 
User avatar
CZFan
Forum Guru
Forum Guru
Posts: 1585
Joined: Sun Oct 09, 2016 8:25 pm
Location: South Africa, Randburg
Contact:

Re: problems resolving IP Cloud addresses

Tue Jun 12, 2018 6:03 pm

@janisk, thank for this, this is proactive info that can be used.

The only suggestion I want to make is to make it a Pinned post or even an "announcement post" for a couple of weeks, else it disappears in the masses and many might not read it
MTCNA, MTCTCE, MTCRE & MTCINE
 
User avatar
Splash
Member Candidate
Member Candidate
Posts: 153
Joined: Fri Oct 16, 2015 10:09 am
Location: Johannesburg, South Africa

Re: problems resolving IP Cloud addresses

Wed Jun 13, 2018 2:45 pm

I am having issues with the resolution of dynamic host names against the new NS servers. A number of requests timeout but some return ok.
dig 1234567890.sn.mynetname.net @ns1.kissthenet.net

; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7 <<>> 1234567890.sn.mynetname.net @ns1.kissthenet.net
;; global options: +cmd
;; connection timed out; no servers could be reached

dig 1234567890.sn.mynetname.net @159.148.172.251   

; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7 <<>> 1234567890.sn.mynetname.net @159.148.172.251
;; global options: +cmd
;; connection timed out; no servers could be reached


dig 1234567890.sn.mynetname.net @159.148.172.251

; <<>> DiG 9.9.4-RedHat-9.9.4-61.el7 <<>> 1234567890.sn.mynetname.net @159.148.172.251
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39734
;; flags: qr aa rd ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;1234567890.sn.mynetname.net. IN      A

;; ANSWER SECTION:
1234567890.sn.mynetname.net. 60 IN    A       11.11.11.11

;; Query time: 263 msec
;; SERVER: 159.148.172.251#53(159.148.172.251)
;; WHEN: Wed Jun 13 13:42:28 SAST 2018
;; MSG SIZE  rcvd: 63
MTCNA, MTCRE, MTCINE, MTCTCE, MTCIPv6E, MTCUME
 
jonthorpe
just joined
Posts: 9
Joined: Mon Oct 27, 2014 3:25 am

Re: problems resolving IP Cloud addresses

Wed Jun 13, 2018 3:15 pm

I'm finding the same thing:
dig +trace 496f022e04ff.sn.mynetname.net 

; <<>> DiG 9.10.6 <<>> +trace 496f022e04ff.sn.mynetname.net
;; global options: +cmd
.			87401	IN	NS	a.root-servers.net.
.			87401	IN	NS	b.root-servers.net.
.			87401	IN	NS	c.root-servers.net.
.			87401	IN	NS	d.root-servers.net.
.			87401	IN	NS	e.root-servers.net.
.			87401	IN	NS	f.root-servers.net.
.			87401	IN	NS	g.root-servers.net.
.			87401	IN	NS	h.root-servers.net.
.			87401	IN	NS	i.root-servers.net.
.			87401	IN	NS	j.root-servers.net.
.			87401	IN	NS	k.root-servers.net.
.			87401	IN	NS	l.root-servers.net.
.			87401	IN	NS	m.root-servers.net.
.			87401	IN	RRSIG	NS 8 0 518400 20180624050000 20180611040000 39570 . qrPNK9BW+EcNETVHvYGuf3cIP7PmfWb6zfikmgYORzMwsn5urzYu6ZPR x/w5jACtOe9ROfqsj1+rxdHr22nWGMz2ZL1ZzfM+ptu1jOK0cunVPwUR Wd4aFk3Dfe9D5uckdNf8x2NuGfpmDa5CXlMiEGv7OF42MIjR5NRZqarZ B3Gx8cWef+PyouWL7rkpCvBHmywisdOE2QSUK8rkBMNyStI5t6Q5yUTj gHujdswu0iYVZfSrKN6p38taWwoIA2Ljf8N2rXsE5T6e+3lK0tYATL0w 1EOpkSVZ90UsLh7/HPE/l6wO91zA5X1uF33LHseLb5U2M4ScNHOQpx0V /OTqaw==
;; Received 525 bytes from 8.8.8.8#53(8.8.8.8) in 27 ms

net.			172800	IN	NS	e.gtld-servers.net.
net.			172800	IN	NS	f.gtld-servers.net.
net.			172800	IN	NS	m.gtld-servers.net.
net.			172800	IN	NS	i.gtld-servers.net.
net.			172800	IN	NS	j.gtld-servers.net.
net.			172800	IN	NS	b.gtld-servers.net.
net.			172800	IN	NS	a.gtld-servers.net.
net.			172800	IN	NS	c.gtld-servers.net.
net.			172800	IN	NS	k.gtld-servers.net.
net.			172800	IN	NS	h.gtld-servers.net.
net.			172800	IN	NS	l.gtld-servers.net.
net.			172800	IN	NS	g.gtld-servers.net.
net.			172800	IN	NS	d.gtld-servers.net.
net.			86400	IN	DS	35886 8 2 7862B27F5F516EBE19680444D4CE5E762981931842C465F00236401D 8BD973EE
net.			86400	IN	RRSIG	DS 8 1 86400 20180626050000 20180613040000 39570 . zOzj9qx3Sd39Nt0jlhdY+zaKs/rDlskXcABihESt0GH/bTa6iR7VTrDR SbrCr+mQEmnnafr+i86VuhdfwDVYuQa+98hpqvZCWuYg/1CL4fA3jLmV 1Yki2gnU0/PIGdCQn+8hpj1BsVaJWoWxSP54yeALB6h3dROkWEx3DWix iQpPLAu8e88EBXDY/nxfqKlN7X6tdfK9yzdtYAh4bxlCGt6CYucbUtJ1 M6keE5MoyD0FbcT1SUHjMQ4pIB4Z7A//OZzTzwMSicn8SftcdpM/hM8S fgvRJH7ogWtGVCAUcrpLRLw3Z9hWD8OhA0N8V6/hBwkSLdfto0h53rUl yjdqrw==
;; Received 1186 bytes from 198.41.0.4#53(a.root-servers.net) in 221 ms

mynetname.net.		172800	IN	NS	ns1.kissthenet.net.
mynetname.net.		172800	IN	NS	ns2.kissthenet.net.
A1RT98BS5QGC9NFI51S9HCI47ULJG6JH.net. 86400 IN NSEC3 1 1 0 - A1RUUFFJKCT2Q54P78F8EJGJ8JBK7I8B  NS SOA RRSIG DNSKEY NSEC3PARAM
A1RT98BS5QGC9NFI51S9HCI47ULJG6JH.net. 86400 IN RRSIG NSEC3 8 2 86400 20180617052733 20180610041733 30812 net. ZLMPVFv995ccHW8VF1priAa0bF2XfMCLegJ08gCAxievCK2d0fZBGOeU xaFB/j0oPRO93BR+7O+2PTSJpdMQoZP35bc327EUn+S+gj7wOlSYNsVA n4rPTbrBwQOiL6V+S8Ycvq6PwWWovylzweMawHtlNCEyd/Q3l4T+Ej/y NC0=
LHCOPAMC6RKK2V6H4DHT88Q0BHSUQPG4.net. 86400 IN NSEC3 1 1 0 - LHDE9UVU9IHC9LO56N7PVQ2EOHT64QL5  NS DS RRSIG
LHCOPAMC6RKK2V6H4DHT88Q0BHSUQPG4.net. 86400 IN RRSIG NSEC3 8 2 86400 20180617052534 20180610041534 30812 net. m9B4edDAytjn1U8vrEEfEy+9Y4nOtV/ofJ9v16FJbOL11n0Xqn0P2AZe V0JSwdno5L+7cfEPdYxIhHD8n3i1P56nHJffBtFCnIlmzfKrAMgxfNkD WghHLWu7uGhmTULfZmo6/7hgfR+kkhV8Sz/qE/d0Mr4WX2vfF1K0o2ig Jcg=
;; Received 622 bytes from 192.31.80.30#53(d.gtld-servers.net) in 262 ms


;; connection timed out; no servers could be reached
And then a few moments later:
; <<>> DiG 9.10.6 <<>> +trace 496f022e04ff.sn.mynetname.net
;; global options: +cmd
.			53122	IN	NS	a.root-servers.net.
.			53122	IN	NS	b.root-servers.net.
.			53122	IN	NS	c.root-servers.net.
.			53122	IN	NS	d.root-servers.net.
.			53122	IN	NS	e.root-servers.net.
.			53122	IN	NS	f.root-servers.net.
.			53122	IN	NS	g.root-servers.net.
.			53122	IN	NS	h.root-servers.net.
.			53122	IN	NS	i.root-servers.net.
.			53122	IN	NS	j.root-servers.net.
.			53122	IN	NS	k.root-servers.net.
.			53122	IN	NS	l.root-servers.net.
.			53122	IN	NS	m.root-servers.net.
.			53122	IN	RRSIG	NS 8 0 518400 20180623170000 20180610160000 39570 . TlaqdC2mq3DhhbEHirly7s+z6YqPGdybAqpsTJZBBB49/6TpArNcL81s mV5rXQr0VuQtsponQfSchOOdlSjdGmEbwFSLSkg1OFSxhaD2nfcgn7Qe 9FXd3ni4mc/flTYNAPtu8FAwA8CP0yZrl6xzKUyhpIGgEALJbNhzpxdv BgzgYJoLM8CHNMDPFGFc+RKvbjpzFrbNCEoeQvYwgIyspg4U91h2IRci +2pt3r44H82ndMKjrl/2nG8yPnRiFaRZIVYe0zCU7Iha45z9wDyNQJ4T zgJrMtMXdUGZV7JWe+T0BXQdYUVZ2TduTFRqY/xtO6mfc6HXD8AP89wb CWgCJQ==
;; Received 525 bytes from 8.8.8.8#53(8.8.8.8) in 48 ms

net.			172800	IN	NS	l.gtld-servers.net.
net.			172800	IN	NS	b.gtld-servers.net.
net.			172800	IN	NS	c.gtld-servers.net.
net.			172800	IN	NS	d.gtld-servers.net.
net.			172800	IN	NS	e.gtld-servers.net.
net.			172800	IN	NS	f.gtld-servers.net.
net.			172800	IN	NS	g.gtld-servers.net.
net.			172800	IN	NS	a.gtld-servers.net.
net.			172800	IN	NS	h.gtld-servers.net.
net.			172800	IN	NS	i.gtld-servers.net.
net.			172800	IN	NS	j.gtld-servers.net.
net.			172800	IN	NS	k.gtld-servers.net.
net.			172800	IN	NS	m.gtld-servers.net.
net.			86400	IN	DS	35886 8 2 7862B27F5F516EBE19680444D4CE5E762981931842C465F00236401D 8BD973EE
net.			86400	IN	RRSIG	DS 8 1 86400 20180626050000 20180613040000 39570 . zOzj9qx3Sd39Nt0jlhdY+zaKs/rDlskXcABihESt0GH/bTa6iR7VTrDR SbrCr+mQEmnnafr+i86VuhdfwDVYuQa+98hpqvZCWuYg/1CL4fA3jLmV 1Yki2gnU0/PIGdCQn+8hpj1BsVaJWoWxSP54yeALB6h3dROkWEx3DWix iQpPLAu8e88EBXDY/nxfqKlN7X6tdfK9yzdtYAh4bxlCGt6CYucbUtJ1 M6keE5MoyD0FbcT1SUHjMQ4pIB4Z7A//OZzTzwMSicn8SftcdpM/hM8S fgvRJH7ogWtGVCAUcrpLRLw3Z9hWD8OhA0N8V6/hBwkSLdfto0h53rUl yjdqrw==
;; Received 1186 bytes from 192.203.230.10#53(e.root-servers.net) in 11 ms

mynetname.net.		172800	IN	NS	ns1.kissthenet.net.
mynetname.net.		172800	IN	NS	ns2.kissthenet.net.
A1RT98BS5QGC9NFI51S9HCI47ULJG6JH.net. 86400 IN NSEC3 1 1 0 - A1RUUFFJKCT2Q54P78F8EJGJ8JBK7I8B  NS SOA RRSIG DNSKEY NSEC3PARAM
A1RT98BS5QGC9NFI51S9HCI47ULJG6JH.net. 86400 IN RRSIG NSEC3 8 2 86400 20180617052733 20180610041733 30812 net. ZLMPVFv995ccHW8VF1priAa0bF2XfMCLegJ08gCAxievCK2d0fZBGOeU xaFB/j0oPRO93BR+7O+2PTSJpdMQoZP35bc327EUn+S+gj7wOlSYNsVA n4rPTbrBwQOiL6V+S8Ycvq6PwWWovylzweMawHtlNCEyd/Q3l4T+Ej/y NC0=
LHCOPAMC6RKK2V6H4DHT88Q0BHSUQPG4.net. 86400 IN NSEC3 1 1 0 - LHDE9UVU9IHC9LO56N7PVQ2EOHT64QL5  NS DS RRSIG
LHCOPAMC6RKK2V6H4DHT88Q0BHSUQPG4.net. 86400 IN RRSIG NSEC3 8 2 86400 20180617052534 20180610041534 30812 net. m9B4edDAytjn1U8vrEEfEy+9Y4nOtV/ofJ9v16FJbOL11n0Xqn0P2AZe V0JSwdno5L+7cfEPdYxIhHD8n3i1P56nHJffBtFCnIlmzfKrAMgxfNkD WghHLWu7uGhmTULfZmo6/7hgfR+kkhV8Sz/qE/d0Mr4WX2vfF1K0o2ig Jcg=
;; Received 622 bytes from 192.41.162.30#53(l.gtld-servers.net) in 154 ms

496f022e04ff.sn.mynetname.net. 60 IN	A	59.167.236.143
;; Received 63 bytes from 159.148.172.251#53(ns2.kissthenet.net) in 556 ms
 
R1CH
Forum Veteran
Forum Veteran
Posts: 919
Joined: Sun Oct 01, 2006 11:44 pm

Re: problems resolving IP Cloud addresses

Wed Jun 13, 2018 4:45 pm

GTLD nameservers are still returning the old records. May want to check that.

https://r-1.ch/r1dns/dnscheck.cgi?domain=mynetname.net
 
quaga
just joined
Posts: 3
Joined: Mon Jun 18, 2018 8:54 pm

Re: problems resolving IP Cloud addresses

Mon Jun 18, 2018 9:28 pm

The problem with DNS persist. Any news about it ?
 
quaga
just joined
Posts: 3
Joined: Mon Jun 18, 2018 8:54 pm

Re: problems resolving IP Cloud addresses

Mon Jun 18, 2018 9:34 pm

The problem still persists, something new?
 
Plutone
just joined
Posts: 15
Joined: Mon Jun 06, 2016 11:48 am

Re: problems resolving IP Cloud addresses

Tue Jun 19, 2018 3:16 pm

GTLD nameservers are still returning the old records. May want to check that.

https://r-1.ch/r1dns/dnscheck.cgi?domain=mynetname.net
I confirm that now glue records of domain mynetname.net are wrong and pointing to
ns1.kissthenet.net (81.198.87.240)
ns2.kissthenet.net (91.188.51.139)

instead of

ns1.kissthenet.net (159.148.147.201)
ns2.kissthenet.net (159.148.172.251)

This has nothing to do with cache, these are GLUE record, or you change them on your domain registrar (publicdomainregistry), or they will never change
 
quaga
just joined
Posts: 3
Joined: Mon Jun 18, 2018 8:54 pm

Re: problems resolving IP Cloud addresses

Thu Jun 28, 2018 1:20 am

the support should fix this configuration urgently!
 
Paternot
Long time Member
Long time Member
Posts: 615
Joined: Thu Jun 02, 2016 4:01 am
Location: Niterói / Brazil

Re: problems resolving IP Cloud addresses

Thu Jun 28, 2018 1:51 am

It is working for me (Brazil). Maybe some geographic cache?
:~> dig ns1.kissthenet.net

; <<>> DiG 9.11.2 <<>> ns1.kissthenet.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11756
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 13, ADDITIONAL: 11

;; QUESTION SECTION:
;ns1.kissthenet.net.            IN      A

;; ANSWER SECTION:
ns1.kissthenet.net.     21492   IN      A       159.148.147.201

;; AUTHORITY SECTION:
net.                    72325   IN      NS      h.gtld-servers.net.
net.                    72325   IN      NS      e.gtld-servers.net.
net.                    72325   IN      NS      i.gtld-servers.net.
net.                    72325   IN      NS      a.gtld-servers.net.
net.                    72325   IN      NS      c.gtld-servers.net.
net.                    72325   IN      NS      g.gtld-servers.net.
net.                    72325   IN      NS      l.gtld-servers.net.
net.                    72325   IN      NS      d.gtld-servers.net.
net.                    72325   IN      NS      b.gtld-servers.net.
net.                    72325   IN      NS      j.gtld-servers.net.
net.                    72325   IN      NS      f.gtld-servers.net.
net.                    72325   IN      NS      k.gtld-servers.net.
net.                    72325   IN      NS      m.gtld-servers.net.

;; ADDITIONAL SECTION:
e.gtld-servers.net.     2568    IN      A       192.12.94.30
i.gtld-servers.net.     15858   IN      A       192.43.172.30
a.gtld-servers.net.     1311    IN      A       192.5.6.30
c.gtld-servers.net.     141625  IN      A       192.26.92.30
l.gtld-servers.net.     72325   IN      A       192.41.162.30
d.gtld-servers.net.     141625  IN      A       192.31.80.30
b.gtld-servers.net.     72325   IN      A       192.33.14.30
j.gtld-servers.net.     72325   IN      A       192.48.79.30
f.gtld-servers.net.     72325   IN      A       192.35.51.30
k.gtld-servers.net.     72325   IN      A       192.52.178.30
m.gtld-servers.net.     72325   IN      A       192.55.83.30

;; Query time: 2 msec
;; SERVER: 10.10.2.1#53(10.10.2.1)
;; WHEN: Wed Jun 27 19:49:35 -03 2018
;; MSG SIZE  rcvd: 449

:~> dig ns2.kissthenet.net

; <<>> DiG 9.11.2 <<>> ns2.kissthenet.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58504
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 13, ADDITIONAL: 11

;; QUESTION SECTION:
;ns2.kissthenet.net.            IN      A

;; ANSWER SECTION:
ns2.kissthenet.net.     21432   IN      A       159.148.172.251

;; AUTHORITY SECTION:
net.                    72252   IN      NS      l.gtld-servers.net.
net.                    72252   IN      NS      d.gtld-servers.net.
net.                    72252   IN      NS      b.gtld-servers.net.
net.                    72252   IN      NS      j.gtld-servers.net.
net.                    72252   IN      NS      f.gtld-servers.net.
net.                    72252   IN      NS      k.gtld-servers.net.
net.                    72252   IN      NS      m.gtld-servers.net.
net.                    72252   IN      NS      h.gtld-servers.net.
net.                    72252   IN      NS      e.gtld-servers.net.
net.                    72252   IN      NS      i.gtld-servers.net.
net.                    72252   IN      NS      a.gtld-servers.net.
net.                    72252   IN      NS      c.gtld-servers.net.
net.                    72252   IN      NS      g.gtld-servers.net.

;; ADDITIONAL SECTION:
l.gtld-servers.net.     72252   IN      A       192.41.162.30
d.gtld-servers.net.     141552  IN      A       192.31.80.30
b.gtld-servers.net.     72252   IN      A       192.33.14.30
j.gtld-servers.net.     72252   IN      A       192.48.79.30
f.gtld-servers.net.     72252   IN      A       192.35.51.30
k.gtld-servers.net.     72252   IN      A       192.52.178.30
m.gtld-servers.net.     72252   IN      A       192.55.83.30
e.gtld-servers.net.     2495    IN      A       192.12.94.30
i.gtld-servers.net.     15785   IN      A       192.43.172.30
a.gtld-servers.net.     1238    IN      A       192.5.6.30
c.gtld-servers.net.     141552  IN      A       192.26.92.30

;; Query time: 2 msec
;; SERVER: 10.10.2.1#53(10.10.2.1)
;; WHEN: Wed Jun 27 19:50:48 -03 2018
;; MSG SIZE  rcvd: 449
 
Plutone
just joined
Posts: 15
Joined: Mon Jun 06, 2016 11:48 am

Re: problems resolving IP Cloud addresses

Thu Jun 28, 2018 2:03 am

It is working for me (Brazil). Maybe some geographic cache?
:~> dig ns1.kissthenet.net

; <<>> DiG 9.11.2 <<>> ns1.kissthenet.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 11756
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 13, ADDITIONAL: 11

;; QUESTION SECTION:
;ns1.kissthenet.net.            IN      A

;; ANSWER SECTION:
ns1.kissthenet.net.     21492   IN      A       159.148.147.201

;; AUTHORITY SECTION:
net.                    72325   IN      NS      h.gtld-servers.net.
net.                    72325   IN      NS      e.gtld-servers.net.
net.                    72325   IN      NS      i.gtld-servers.net.
net.                    72325   IN      NS      a.gtld-servers.net.
net.                    72325   IN      NS      c.gtld-servers.net.
net.                    72325   IN      NS      g.gtld-servers.net.
net.                    72325   IN      NS      l.gtld-servers.net.
net.                    72325   IN      NS      d.gtld-servers.net.
net.                    72325   IN      NS      b.gtld-servers.net.
net.                    72325   IN      NS      j.gtld-servers.net.
net.                    72325   IN      NS      f.gtld-servers.net.
net.                    72325   IN      NS      k.gtld-servers.net.
net.                    72325   IN      NS      m.gtld-servers.net.

;; ADDITIONAL SECTION:
e.gtld-servers.net.     2568    IN      A       192.12.94.30
i.gtld-servers.net.     15858   IN      A       192.43.172.30
a.gtld-servers.net.     1311    IN      A       192.5.6.30
c.gtld-servers.net.     141625  IN      A       192.26.92.30
l.gtld-servers.net.     72325   IN      A       192.41.162.30
d.gtld-servers.net.     141625  IN      A       192.31.80.30
b.gtld-servers.net.     72325   IN      A       192.33.14.30
j.gtld-servers.net.     72325   IN      A       192.48.79.30
f.gtld-servers.net.     72325   IN      A       192.35.51.30
k.gtld-servers.net.     72325   IN      A       192.52.178.30
m.gtld-servers.net.     72325   IN      A       192.55.83.30

;; Query time: 2 msec
;; SERVER: 10.10.2.1#53(10.10.2.1)
;; WHEN: Wed Jun 27 19:49:35 -03 2018
;; MSG SIZE  rcvd: 449

:~> dig ns2.kissthenet.net

; <<>> DiG 9.11.2 <<>> ns2.kissthenet.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 58504
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 13, ADDITIONAL: 11

;; QUESTION SECTION:
;ns2.kissthenet.net.            IN      A

;; ANSWER SECTION:
ns2.kissthenet.net.     21432   IN      A       159.148.172.251

;; AUTHORITY SECTION:
net.                    72252   IN      NS      l.gtld-servers.net.
net.                    72252   IN      NS      d.gtld-servers.net.
net.                    72252   IN      NS      b.gtld-servers.net.
net.                    72252   IN      NS      j.gtld-servers.net.
net.                    72252   IN      NS      f.gtld-servers.net.
net.                    72252   IN      NS      k.gtld-servers.net.
net.                    72252   IN      NS      m.gtld-servers.net.
net.                    72252   IN      NS      h.gtld-servers.net.
net.                    72252   IN      NS      e.gtld-servers.net.
net.                    72252   IN      NS      i.gtld-servers.net.
net.                    72252   IN      NS      a.gtld-servers.net.
net.                    72252   IN      NS      c.gtld-servers.net.
net.                    72252   IN      NS      g.gtld-servers.net.

;; ADDITIONAL SECTION:
l.gtld-servers.net.     72252   IN      A       192.41.162.30
d.gtld-servers.net.     141552  IN      A       192.31.80.30
b.gtld-servers.net.     72252   IN      A       192.33.14.30
j.gtld-servers.net.     72252   IN      A       192.48.79.30
f.gtld-servers.net.     72252   IN      A       192.35.51.30
k.gtld-servers.net.     72252   IN      A       192.52.178.30
m.gtld-servers.net.     72252   IN      A       192.55.83.30
e.gtld-servers.net.     2495    IN      A       192.12.94.30
i.gtld-servers.net.     15785   IN      A       192.43.172.30
a.gtld-servers.net.     1238    IN      A       192.5.6.30
c.gtld-servers.net.     141552  IN      A       192.26.92.30

;; Query time: 2 msec
;; SERVER: 10.10.2.1#53(10.10.2.1)
;; WHEN: Wed Jun 27 19:50:48 -03 2018
;; MSG SIZE  rcvd: 449
Again, this is not cache or something like that geographical, this is a miss change after switching to new nameserver. They only have to change 2 glue record (20 secs operation on registrar provider).

To test, launch this dig query

dig ns mynetname.net @a.gtld-servers.net

And you will see the old ns1 and ns2 glue record.
 
infused
Member
Member
Posts: 308
Joined: Fri Dec 28, 2012 2:33 pm

Re: problems resolving IP Cloud addresses

Thu Jun 28, 2018 6:04 am

Whats the IP meant to be for the licensing server? Can't register a bunch of licenses. Causing me a headache.
 
Paternot
Long time Member
Long time Member
Posts: 615
Joined: Thu Jun 02, 2016 4:01 am
Location: Niterói / Brazil

Re: problems resolving IP Cloud addresses

Thu Jun 28, 2018 5:14 pm

Again, this is not cache or something like that geographical, this is a miss change after switching to new nameserver. They only have to change 2 glue record (20 secs operation on registrar provider).

To test, launch this dig query

dig ns mynetname.net @a.gtld-servers.net

And you will see the old ns1 and ns2 glue record.
Ah, true enough. :D
 
Plutone
just joined
Posts: 15
Joined: Mon Jun 06, 2016 11:48 am

Re: problems resolving IP Cloud addresses

Tue Jul 03, 2018 5:52 pm

Finally they have updated the glue records:
Now it works

dig ns mynetname.net @c.gtld-servers.net

; <<>> DiG 9.10.3-P4-Debian <<>> ns mynetname.net @c.gtld-servers.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53924
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 5
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;mynetname.net. IN NS

;; AUTHORITY SECTION:
mynetname.net. 172800 IN NS ns2.kissthenet.net.
mynetname.net. 172800 IN NS ns1.kissthenet.net.

;; ADDITIONAL SECTION:
ns2.kissthenet.net. 172800 IN A 159.148.172.251
ns2.kissthenet.net. 172800 IN AAAA 2a02:610:7501:4000::251
ns1.kissthenet.net. 172800 IN A 159.148.147.201
ns1.kissthenet.net. 172800 IN AAAA 2a02:610:7501:1000::201

;; Query time: 42 msec
;; SERVER: 192.26.92.30#53(192.26.92.30)
;; WHEN: Tue Jul 03 16:51:53 CEST 2018
;; MSG SIZE rcvd: 177

Who is online

Users browsing this forum: MSN [Bot] and 112 guests