Yes, I can even approve that from my own experiences with UTL dns
servers. But that is how its supposed to work and it does usually
outside of UG.
;; QUESTION SECTION:
;mountbattenhosting.net. IN NS
;; ANSWER SECTION:
mountbattenhosting.net. 7115 IN NS
nsusam1s.mountbattenhosting.net.
mountbattenhosting.net. 7115 IN NS
nsugam1m.mountbattenhosting.net.
;; ADDITIONAL SECTION:
nsugam1m.mountbattenhosting.net. 83748 IN A 41.220.5.16
nsusam1s.mountbattenhosting.net. 83748 IN A 208.79.240.3
The NS records are on a 24hour TTL at moment which is the recommended
standard.
Rgds,
Rocco
On 09/04/2010 12:53, McTim wrote:
On Fri, Apr 9, 2010 at 12:42 PM, IT-Doc24 Ltd. - Rocco Radisch
<[email protected]> wrote:
For that we have the TTL (time to live) value in the DNS records. Lower the
TTL value to 300 (5 mins) of the respective record 24 hours before the
change then other DNS servers / caches / clients are instructed to check
back within the given time. After the change you can go back to 24hours
(86400). If ISPs have a fixed cache time out that would be against the IETF.
ISPs (and other network operators) everywhere including UG are non-RFC
compliant in one way or another.
_______________________________________________
LUG mailing list
[email protected]
http://kym.net/mailman/listinfo/lug
LUG is generously hosted by INFOCOM http://www.infocom.co.ug/
All Archives can be found at http://www.mail-archive.com/[email protected]/
The above comments and data are owned by whoever posted them (including
attachments if any). The List's Host is not responsible for them in any way.
---------------------------------------
