Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Problem changing name server on .de domain

Status
Not open for further replies.

Fox1977

IS-IT--Management
Dec 6, 2001
98
GB
Hi there,

Just wondering if anyone can help me out with this one. I have registered a .de domain through total registrations and i am having a bit of trouble changing the name servers over to our own.

I have tried to change the domain server several times with no luck. Total registrations are saying that the name server change failed after several DNS errors. After several days pestering them then told us what the error was:

checking SOA Record:
SOA origin: xxxxxxx
SOA mail: xxxxxxx
SOA serial: 2007121202
SOA refresh: 7200
SOA retry: 3600
SOA expire: 604800
SOA minttl: 86400
ERROR: SOA refresh (7200) is too small (10000 <= refresh <= 86400) on nameserver 'xxxxxxxxxxx [81.201.143.133]'I am thinking that this is down to the specific country requirements set by denic. See here:

All the authoritative name servers for the new zone must be indicated. Also, all the matching SOA records (SOA = Start Of Authority) must be uniform and must fall within the following guidance values (indicated in seconds):
refresh : 10000 - 86400
retry: 1800 -28800
expire: 604800 - 3600000
ttl: 180 - 345600

I am in the process of getting custom TTL records setup on our name servers so we can alter the SOA/TTL records to try and sort it.

Has anyone had any similar problems with .de domains or offer any advice?
Can anyone recommend agood company whose name servers meet with the Denic requirements?

Thanks
 
It isn't the TTL that it is complaining, this is the refresh time or the interval for your secondaries. Secondly, you are changing servers to your own, just change it to 10000, repoint the servers, then change it back to what you want. They won't/shouldn't care (unless they are secondaries for you).
Thirdly, since this is only the default refresh time, you can use NOTIFY (bind) or some other push method to get updates to your secondaries (if you control them).
 
We managed to get custom TTLs switched on on our dns servers and it cured the problems.

The denic registry have really specific DNS server requirements. All running fine now.

thanks
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top