2011/6/19 babu dheen
>
> Hi,
>
> I have a DNS server running in BIND. I executed to take backup of
> configuration and zone files as below and its working fine.
>
> # /bin/tar -pczvf named.tar.gz /etc/ /var/named
> --exclude='/var/named/chroot/var/named/data'
> --exclude='/var/named/chroot/pro
2011/6/19 David Miller :
>
> In the particular case of the OP - example.net. has name servers under
> example.com.
>
> To make lookups for records under example.net., resolvers walk the tree from
> "." to "net." and get NS records - ns1.example.com. and ns2.example.com.
>
> You can't insert glue re
2011/6/19 Michael Sinatra :
> On 06/18/11 15:23, Chris Thompson wrote:
>>
>
>> Of course, at the root zone level, *all* NS records need either
>> "required glue" or "sibling glue", because every single one of them
>> is somewhere under the root zone. At least, until the aliens contact
>> us and we
Greetings,
given my domain name is example.net, and my NS servers for example.net are:
ns1.example.com
ns2.example.com
But, example.com itself's NS servers are the registrator's (for
example, godaddy's).
Under this case, I don't need any glue for ns[1-2].example.com.
But why I still need to reg
Thanks Michael.
I appreciate it much.
2010/12/20 Michael Sinatra :
> On 12/19/10 23:47, Jorg W Young wrote:
>>
>> Hello,
>>
>> We primarily update the DNS records by nsupdate from a web interface.
>> Under this case, if I modified the zone file directly by han
Hello,
We primarily update the DNS records by nsupdate from a web interface.
Under this case, if I modified the zone file directly by hand, will
nsupdate overwrite the modification?
Thanks.
___
bind-users mailing list
bind-users@lists.isc.org
https://li
2010/12/12 Barry Margolin :
> The two servers for your domain have different versions of the zone.
>
> ns1.dns-diy.com has serial number 3556 and the record:
>
> s3.xxfy.duowan.com. 300 IN CNAME s3-duowan.xxfy.kunlun.com.
>
> ns2.dns-diy.com has serial number 3551 and is missing that record, so
Hello,
One of our records, s3.xxfy.duowan.com, has been meeting the resolving problem.
The different dns cache will get different result for the resolving.
for example,
$ dig s3.xxfy.duowan.com @202.96.128.166 +short
s3-duowan.xxfy.kunlun.com.
60.28.208.177
$ dig s3.xxfy.duowan.com @8.8.8.8 +sh
f there is DNS query statistics.
We have been greatest expecting the solid and professional DNS hosting
service, the price is no problem.
If there is any commercial hosting provider here you could please
contact with me.
Thanks.
Kind regrads,
Jorg W. Young
__
9 matches
Mail list logo
