Out of curiosity, could it be something to do with the fact that I used to have ns1 and ns2 set up on an old server and those records haven't been removed from the tld servers?
This level of DNS is something I do so infrequently I end up having to relearn it all over again.
Regards, Ashley Glenday * The time for my yearly haircut is coming around again (March 11th-13th). If anyone wants to sponsor me they can make a tax deductible donation at: http://my.imisfriendraising.com.au/personalPage.aspx?SID=91562 All money raised goes to the Leukemia Foundation. * ** I will be out of the country between 1st April and 20th April. During this time I can still be reached by email, but will be without mobile contact ** I am now offering after hours services. 7am-9am and 5pm-11pm Weekdays and all day Saturday and Sunday. The after hours number is: 02 4786 0736 New charges will apply Telephone support - $50 Remote support - $100 Onsite support - $200 p/h or part thereof On 20/02/10 11:56, John Ferlito wrote:
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 jo...@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. jo...@zoot:~$ dig soa com ;; ANSWER SECTION: com. 789 IN SOA a.gtld-servers.net. nstld.verisign-grs.com. 1266627161 1800 900 604800 86400 jo...@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
<<attachment: ashley.vcf>>
-- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
