- To: Ashley Glenday <ashley@xxxxxxxxxxxxxxxxxxx>
- Subject: Re: [SLUG] Testing glue records
- From: John Ferlito <johnf@xxxxxxxxxx>
- Date: Sat, 20 Feb 2010 11:56:35 +1100
- Cc: slug@xxxxxxxxxxx
- User-agent: Mutt/1.5.20 (2009-06-14)
On Fri, Feb 19, 2010 at 11:12:44PM +1100, Ashley Glenday wrote:
> At the beginning of this saga I had a server in America that I
> called ns1.domain.com and ns2.domain.com. After this I decided to
> become patriotic (with the help of some sluggers suggestions) and
> moved to a host in Sydney, this server became ns3.domain.com and
> ns4.domain.com. My problem is that it's time to move yet again and I
> wanted to go back to ns1.domain.com and ns2.domain.com but this
> doesn't seem to work. My registrar assures me they've set the glue
> records up properly but I can't get it to resolve. The host has set
> the reverse DNS up as I can confirm that with host 123.123.123.123
> which returns ns1.domain.com
>
> What I'm after is any known way to test the glue records are in fact
> set up properly and if they are, what else could I have missed?
So for google If I wanted to check I would do
johnf@zoot:~$ dig ns google.com
;; ANSWER SECTION:
google.com. 296819 IN NS ns4.google.com.
google.com. 296819 IN NS ns2.google.com.
google.com. 296819 IN NS ns1.google.com.
google.com. 296819 IN NS ns3.google.com.
johnf@zoot:~$ dig soa com
;; ANSWER SECTION:
com. 789 IN SOA a.gtld-servers.net. nstld.verisign-grs.com. 1266627161 1800 900 604800 86400
johnf@zoot:~$ dig a ns1.google.com. @a.gtld-servers.net.
;; ANSWER SECTION:
ns1.google.com. 172800 IN A 216.239.32.10
If there is no glue record the ANSWER section will be empty and you'll
get a WARNING about recusrion being disabled.
Cheers,
John
--
John
Blog http://www.inodes.org
LCA2010 http://www.lca2010.org.nz