domain A-record question

antic

Perch
Setting up a new reseller domain on cluster 2, and noticed something odd about the domain in my registrar's control panel.. everything seems to be working OK, including DNS and CP. However I had these A records which looked strange. Again, this is at the registrar, not in HSphere:

@.myservicedomain.net.au - 203.17.36.111
ctl.myservicedomain.net.au - 203.17.36.111
ftp.myservicedomain.net.au - 203.17.36.111
mail.myservicedomain.net.au - 203.17.36.40
www.myservicedomain.net.au - 203.17.36.111

No A-records for my custom DNS (ns1 and ns2) but I don't think any are needed - they are set up under a different section, "hostnames". Anyway, the ones above looked odd, as they don't point anywhere useful, so I .. err.. just deleted them. :)

I hope that's ok. Everything still seems to be working. The dns servers for "myservicedomain.net.au" are set to "ns1.myservicedomain.net.au" and "ns2.myservicedomain.net.au", "ns1" and "ns2" are set to the correct Cluster 2 DNS IP's under the registrar's "hostnames" section. And yet these A-records remain unaffected and seemingly entirely unrelated to anything.

So the question is, are those A-records supposed to be there? I assumed they were pointing to a server belonging to the registrar for parking purposes.. so was it ok to remove them? I checked another domain at the same registrar, and the same set of A-records are there, pointing to the same IPs. What are they for, and do they interfere at all with normal resolution of the domain name? Should they be removed or left alone, or set to something specific? Is there such a thing as domain paranoia? :twitch:
 
should be OK to remove they belong to infobahn in Australia who looks to be an all around provider from internet to hosting and domain purchasing.
 
Cool... so in other words, setting the dns server overrides anything in the A records? Funny, I woulda thought it would be the other way around.. unless of course it's the HSphere A-record settings that override it, since that's set to be the controlling dns... ok, makes sense now. :)
 
Yes godaddy does something simialr as well, but when you set the nameservers away from their parked servers, they don't work.
 
Back
Top