Re: resolution problem
In article , Matus UHLAR - fantomas wrote: often a problem of invalid NS delegation, or bad TTL (A record for a server expires before NS record). On 19.05.16 15:31, Sam Wilson wrote: Glue A records for the nameservers have 172800 TTL, authoritative A records have 1200. that's it! ;; ANSWER SECTION: colostate.edu. 3600IN NS dns3.colostate.edu. colostate.edu. 3600IN NS dns1.colostate.edu. ;; ADDITIONAL SECTION: dns3.colostate.edu. 1200IN A 129.82.103.111 dns1.colostate.edu. 1200IN A 129.82.103.121 after 1200 seconds, the A records expire, but the NS records don't. Next 2400 seconds you know that you have to ask dns3.colostate.edu and dns1.colostate.edu, but you can't find their IPs, because ... you don't know their IPs. while some DNS servers can cope with that, it's still broken setup. On 24.05.16 11:14, Thomas Schulz wrote: Our server here running BIND 9.10.3-P4 seems to handle it OK. Do some versions of Bind work with this broken setup while other versions do not? I wonder what versions of Bind are running on the two servers that do work and what versions on the two that do not. I can't tell you under what circumstances it works and when it doesn't. I can only repeat that this setup is broken and why. There's no point of complaining before it's fixed, it's just ranting: "I have broken setup and it doesn't work on some servers..." -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Spam = (S)tupid (P)eople's (A)dvertising (M)ethod ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: resolution problem
colostate.edu. 172800 IN NS dns1.colostate.edu. colostate.edu. 172800 IN NS dns3.colostate.edu. ;; Received 119 bytes from 192.41.162.30#53(l.edu-servers.net) in 78 ms www.cloudsat.cira.colostate.edu. 3600 IN CNAME dpc.cira.colostate.edu. dpc.cira.colostate.edu. 3600IN A 129.82.109.62 ;; Received 83 bytes from 129.82.103.121#53(dns1.colostate.edu) in 36 ms > >>In article , >> Matus UHLAR - fantomas wrote: >>> often a problem of invalid NS delegation, or bad TTL (A record for a server >>> expires before NS record). > > On 19.05.16 15:31, Sam Wilson wrote: >>Glue A records for the nameservers have 172800 TTL, authoritative A >>records have 1200. > > that's it! > > ;; ANSWER SECTION: > colostate.edu. 3600IN NS dns3.colostate.edu. > colostate.edu. 3600IN NS dns1.colostate.edu. > > ;; ADDITIONAL SECTION: > dns3.colostate.edu. 1200IN A 129.82.103.111 > dns1.colostate.edu. 1200IN A 129.82.103.121 > > after 1200 seconds, the A records expire, but the NS records don't. > > Next 2400 seconds you know that you have to ask dns3.colostate.edu and > dns1.colostate.edu, but you can't find their IPs, because ... you don't > know their IPs. > > while some DNS servers can cope with that, it's still broken setup. Our server here running BIND 9.10.3-P4 seems to handle it OK. Do some versions of Bind work with this broken setup while other versions do not? I wonder what versions of Bind are running on the two servers that do work and what versions on the two that do not. > -- > Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ > Warning: I wish NOT to receive e-mail advertising to this address. > Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. > I feel like I'm diagonally parked in a parallel universe. Tom Schulz Applied Dynamics Intl. sch...@adi.com ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: resolution problem
>colostate.edu. 172800 IN NS dns1.colostate.edu. >colostate.edu. 172800 IN NS dns3.colostate.edu. >;; Received 119 bytes from 192.41.162.30#53(l.edu-servers.net) in 78 ms > >www.cloudsat.cira.colostate.edu. 3600 IN CNAME dpc.cira.colostate.edu. >dpc.cira.colostate.edu. 3600IN A 129.82.109.62 >;; Received 83 bytes from 129.82.103.121#53(dns1.colostate.edu) in 36 ms In article , Matus UHLAR - fantomas wrote: often a problem of invalid NS delegation, or bad TTL (A record for a server expires before NS record). On 19.05.16 15:31, Sam Wilson wrote: Glue A records for the nameservers have 172800 TTL, authoritative A records have 1200. that's it! ;; ANSWER SECTION: colostate.edu. 3600IN NS dns3.colostate.edu. colostate.edu. 3600IN NS dns1.colostate.edu. ;; ADDITIONAL SECTION: dns3.colostate.edu. 1200IN A 129.82.103.111 dns1.colostate.edu. 1200IN A 129.82.103.121 after 1200 seconds, the A records expire, but the NS records don't. Next 2400 seconds you know that you have to ask dns3.colostate.edu and dns1.colostate.edu, but you can't find their IPs, because ... you don't know their IPs. while some DNS servers can cope with that, it's still broken setup. -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. I feel like I'm diagonally parked in a parallel universe. ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: resolution problem
In article , Matus UHLAR - fantomas wrote: > On 18.05.16 14:10, Con Wieland wrote: > >I am having an issue resolving www.cloudsat.cira.colostate.edu from 2 of my > > name servers. I have 2 others with identical configs that resolve > > correctly. A normal lookup shows a server fail but a +trace looks ok. > > Any ideas how to better troubleshoot the issue? > > tried web dns checkers? Some of them use to provide useful results. > > >dig www.cloudsat.cira.colostate.edu @ns1.service.uci.edu > [...] > >;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 1057 > > > >colostate.edu. 172800 IN NS dns1.colostate.edu. > >colostate.edu. 172800 IN NS dns3.colostate.edu. > >;; Received 119 bytes from 192.41.162.30#53(l.edu-servers.net) in 78 ms > > > >www.cloudsat.cira.colostate.edu. 3600 IN CNAME dpc.cira.colostate.edu. > >dpc.cira.colostate.edu. 3600IN A 129.82.109.62 > >;; Received 83 bytes from 129.82.103.121#53(dns1.colostate.edu) in 36 ms > > often a problem of invalid NS delegation, or bad TTL (A record for a server > expires before NS record). Glue A records for the nameservers have 172800 TTL, authoritative A records have 1200. Sam -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336. ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: resolution problem
On 18/05/16 22:10, Con Wieland wrote: I am having an issue resolving www.cloudsat.cira.colostate.edu "rndc dumpdb" can be helpful in this case, IME. Dump the cache then inspect the records and parent delegations, see what bind thinks is in-cache when it's broken. ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: resolution problem
On 18.05.16 14:10, Con Wieland wrote: I am having an issue resolving www.cloudsat.cira.colostate.edu from 2 of my name servers. I have 2 others with identical configs that resolve correctly. A normal lookup shows a server fail but a +trace looks ok. Any ideas how to better troubleshoot the issue? tried web dns checkers? Some of them use to provide useful results. dig www.cloudsat.cira.colostate.edu @ns1.service.uci.edu [...] ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 1057 colostate.edu. 172800 IN NS dns1.colostate.edu. colostate.edu. 172800 IN NS dns3.colostate.edu. ;; Received 119 bytes from 192.41.162.30#53(l.edu-servers.net) in 78 ms www.cloudsat.cira.colostate.edu. 3600 IN CNAME dpc.cira.colostate.edu. dpc.cira.colostate.edu. 3600IN A 129.82.109.62 ;; Received 83 bytes from 129.82.103.121#53(dns1.colostate.edu) in 36 ms often a problem of invalid NS delegation, or bad TTL (A record for a server expires before NS record). -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. 99 percent of lawyers give the rest a bad name. ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
resolution problem
I am having an issue resolving www.cloudsat.cira.colostate.edu from 2 of my name servers. I have 2 others with identical configs that resolve correctly. A normal lookup shows a server fail but a +trace looks ok. Any ideas how to better troubleshoot the issue? dig www.cloudsat.cira.colostate.edu @ns1.service.uci.edu ; <<>> DiG 9.3.4-P1 <<>> www.cloudsat.cira.colostate.edu @ns1.service.uci.edu ; (1 server found) ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 1057 ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0 ;; QUESTION SECTION: ;www.cloudsat.cira.colostate.edu. INA ;; Query time: 4992 msec ;; SERVER: 128.200.1.201#53(128.200.1.201) ;; WHEN: Wed May 18 14:08:26 2016 ;; MSG SIZE rcvd: 49 dig www.cloudsat.cira.colostate.edu @ns1.service.uci.edu +trace ; <<>> DiG 9.3.4-P1 <<>> www.cloudsat.cira.colostate.edu @ns1.service.uci.edu +trace ; (1 server found) ;; global options: printcmd . 350434 IN NS d.root-servers.net. . 350434 IN NS e.root-servers.net. . 350434 IN NS c.root-servers.net. . 350434 IN NS a.root-servers.net. . 350434 IN NS l.root-servers.net. . 350434 IN NS f.root-servers.net. . 350434 IN NS g.root-servers.net. . 350434 IN NS i.root-servers.net. . 350434 IN NS j.root-servers.net. . 350434 IN NS b.root-servers.net. . 350434 IN NS k.root-servers.net. . 350434 IN NS m.root-servers.net. . 350434 IN NS h.root-servers.net. ;; Received 496 bytes from 128.200.1.201#53(128.200.1.201) in 2 ms edu.172800 IN NS l.edu-servers.net. edu.172800 IN NS a.edu-servers.net. edu.172800 IN NS d.edu-servers.net. edu.172800 IN NS f.edu-servers.net. edu.172800 IN NS g.edu-servers.net. edu.172800 IN NS c.edu-servers.net. ;; Received 284 bytes from 199.7.91.13#53(d.root-servers.net) in 73 ms colostate.edu. 172800 IN NS dns1.colostate.edu. colostate.edu. 172800 IN NS dns3.colostate.edu. ;; Received 119 bytes from 192.41.162.30#53(l.edu-servers.net) in 78 ms www.cloudsat.cira.colostate.edu. 3600 IN CNAME dpc.cira.colostate.edu. dpc.cira.colostate.edu. 3600IN A 129.82.109.62 ;; Received 83 bytes from 129.82.103.121#53(dns1.colostate.edu) in 36 ms___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: named resolution problem
On 05.10.2011 12:58, Roberto Bosticardo wrote: > If you ask a resolver/cache server running named the resolution of name > "www.myspace.fr" it returns (SERVFAIL), if you ask the same to a > dnscache server it correctly resolves to the ip address. BIND doesn't like NS records resolving to CNAMEs: The domain is delegated to two servers: myspace.fr. 60 IN NS ns1.myspace.com. myspace.fr. 60 IN NS ns2.myspace.com. Resolving the server names reveals CNAMEs: ns1.myspace.com.60 IN CNAME DNS11.COTDNS.net. ns2.myspace.com.60 IN CNAME DNS12.COTDNS.net. That is a configuation error at myspace.com and BIND returns SERVFAIL. Unbound and dnscache are more forgiving in this case. Hauke. signature.asc Description: OpenPGP digital signature ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
named resolution problem
Hi all, I have a problem with named (both bind9.3 and bind9.7) and resolution of "www.myspace.fr"; the problem is not present in dnscache (of djbdns suite) or asking resolution to google public dns (they run a Google implementation of dns protocol). If you ask a resolver/cache server running named the resolution of name "www.myspace.fr" it returns (SERVFAIL), if you ask the same to a dnscache server it correctly resolves to the ip address. The problem seems related to two CNAME resolution with tools of bind suite (the problem is present also with dig, I think it uses the same routine of named). the answer section from a working resolver is something like: www.myspace.fr. 86395 IN CNAME wwwi.myspace.com. wwwi.myspace.com. 3595IN CNAME www-lb.myspaceweb.akadns.net. www-lb.myspaceweb.akadns.net. 30 IN A 216.178.39.11 asking to a named resolver it seems it cannot resolve the last cname www.myspace.fr. 86395 IN CNAME wwwi.myspace.com. wwwi.myspace.com. 3595IN CNAME www-lb.myspaceweb.akadns.net. Simulating the recursion, going top down from root nameservers, and asking as the last step the resolution of "www-lb.myspaceweb.akadns.net" to "ze.akadns.net" or one of the other autoritarive akadns server it give the correct ip address. The path seems this: . -> .fr. -> .myspace.fr. autoritative for myspace.fr. are ns1.myspace.com and ns2.myspace.com asking A records for www.myspace.fr to ns1.myspace.com it gives you the two CNAME Named seems unable to resolve this CNAME. I tried to deep debug the problem without success. We have customers affected by this problem and we solved with the definition of a zone for myspace.fr that forwards to a djbdns dnscache server that correctly resolves; This is intended as workaround till we will fix the problem on named/bind. I also suspected it was something related do EDNS0 but i quite sure this is not the problem because google public dns resolver implement EDNS and they don't have the problem. Are your named servers affected by the same problem ? Can you try this name resolution on your servers ? Have you any idea on how to solve the problem ? Have you further tests to suggest us ? Thanx for you patience and forgive me for my bad english Hope someone can help Bye ___ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: BIND 9 And Short Name resolution Problem
In message <4d956ac7.2010...@data.pl>, Torinthiel writes:
> On 03/31/11 20:58, Barry Finkel wrote:
> > On 03/31/11 13:17, bind-users-requ...@lists.isc.org wrote:
> >> Hello,
> >>
> >> I get the following messages on the BIND server when I do a short name=
>
> >> nslookup from a client:
> >>
> >> Mar 31 14:08:04 jedi named[1299]: [ID 873579 daemon.info] network
> >> unreachable resolving 'C.ROOT-SERVERS.NET//IN':
> >> 2001:500:1::803f:235#53
> >> Mar 31 14:08:05 jedi named[1299]: [ID 873579 daemon.info] network
> >> unreachable resolving 'I.ROOT-SERVERS.NET//IN':
> >> 2001:500:1::803f:235#53
> >> Mar 31 14:08:07 jedi named[1299]: [ID 873579 daemon.info] network
> >> unreachable resolving 'B.ROOT-SERVERS.NET//IN': 2001:500:2f::f#53
> >> Mar 31 14:08:07 jedi named[1299]: [ID 873579 daemon.info] network
> >> unreachable resolving 'L.ROOT-SERVERS.NET//IN': 2001:500:2f::f#53
> >>
> >> The config files are below, we are running BIND 9 on Solaris 10. We
> >> currently have 2 domain names configured and on IP address on the BIND=
>
> >> server itself. Any ideas from the gurus??
> >>
> >> Thanks
> >=20
> > You do not have IPv6 connectivity from the DNS server to
> > {C,I,B,L}.root-servers.net.
>
> And is it possible to make BIND stop trying to use IPv6 at all? I'm in a
> similar situation, I know I have connection issues and I simply want
> bind to either not use IPv6 or at least prefer IPv4.
> liste-on-v6 {none;} in named.conf does not help, and I'm not much
> surprised, as it's about listening and not querying.
> Torinthiel
named -4
If you need to be more selective see "server".
e.g.
To just use 6to4 homed server.
server ::/0 { bogus yes; };
server 2002::/16 { bogus no; };
Mark
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: ma...@isc.org
___
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
Re: BIND 9 And Short Name resolution Problem
On 03/31/11 20:58, Barry Finkel wrote:
> On 03/31/11 13:17, bind-users-requ...@lists.isc.org wrote:
>> Hello,
>>
>> I get the following messages on the BIND server when I do a short name
>> nslookup from a client:
>>
>> Mar 31 14:08:04 jedi named[1299]: [ID 873579 daemon.info] network
>> unreachable resolving 'C.ROOT-SERVERS.NET//IN':
>> 2001:500:1::803f:235#53
>> Mar 31 14:08:05 jedi named[1299]: [ID 873579 daemon.info] network
>> unreachable resolving 'I.ROOT-SERVERS.NET//IN':
>> 2001:500:1::803f:235#53
>> Mar 31 14:08:07 jedi named[1299]: [ID 873579 daemon.info] network
>> unreachable resolving 'B.ROOT-SERVERS.NET//IN': 2001:500:2f::f#53
>> Mar 31 14:08:07 jedi named[1299]: [ID 873579 daemon.info] network
>> unreachable resolving 'L.ROOT-SERVERS.NET//IN': 2001:500:2f::f#53
>>
>> The config files are below, we are running BIND 9 on Solaris 10. We
>> currently have 2 domain names configured and on IP address on the BIND
>> server itself. Any ideas from the gurus??
>>
>> Thanks
>
> You do not have IPv6 connectivity from the DNS server to
> {C,I,B,L}.root-servers.net.
And is it possible to make BIND stop trying to use IPv6 at all? I'm in a
similar situation, I know I have connection issues and I simply want
bind to either not use IPv6 or at least prefer IPv4.
liste-on-v6 {none;} in named.conf does not help, and I'm not much
surprised, as it's about listening and not querying.
Torinthiel
signature.asc
Description: OpenPGP digital signature
___
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
Re: BIND 9 And Short Name resolution Problem
On 03/31/11 13:17, bind-users-requ...@lists.isc.org wrote:
Hello,
I get the following messages on the BIND server when I do a short name
nslookup from a client:
Mar 31 14:08:04 jedi named[1299]: [ID 873579 daemon.info] network
unreachable resolving 'C.ROOT-SERVERS.NET//IN': 2001:500:1::803f:235#53
Mar 31 14:08:05 jedi named[1299]: [ID 873579 daemon.info] network
unreachable resolving 'I.ROOT-SERVERS.NET//IN': 2001:500:1::803f:235#53
Mar 31 14:08:07 jedi named[1299]: [ID 873579 daemon.info] network
unreachable resolving 'B.ROOT-SERVERS.NET//IN': 2001:500:2f::f#53
Mar 31 14:08:07 jedi named[1299]: [ID 873579 daemon.info] network
unreachable resolving 'L.ROOT-SERVERS.NET//IN': 2001:500:2f::f#53
The config files are below, we are running BIND 9 on Solaris 10. We
currently have 2 domain names configured and on IP address on the BIND
server itself. Any ideas from the gurus??
Thanks
You do not have IPv6 connectivity from the DNS server to
{C,I,B,L}.root-servers.net.
--
--
Barry S. Finkel
Computing and Information Systems Division
Argonne National Laboratory Phone:+1 (630) 252-7277
9700 South Cass Avenue Facsimile:+1 (630) 252-4601
Building 240, Room 5.B.8 Internet: bsfin...@anl.gov
Argonne, IL 60439-4828 IBMMAIL: I1004994
___
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
BIND 9 And Short Name resolution Problem
Hello,
I get the following messages on the BIND server when I do a short name
nslookup from a client:
Mar 31 14:08:04 jedi named[1299]: [ID 873579 daemon.info] network
unreachable resolving 'C.ROOT-SERVERS.NET//IN': 2001:500:1::803f:235#53
Mar 31 14:08:05 jedi named[1299]: [ID 873579 daemon.info] network
unreachable resolving 'I.ROOT-SERVERS.NET//IN': 2001:500:1::803f:235#53
Mar 31 14:08:07 jedi named[1299]: [ID 873579 daemon.info] network
unreachable resolving 'B.ROOT-SERVERS.NET//IN': 2001:500:2f::f#53
Mar 31 14:08:07 jedi named[1299]: [ID 873579 daemon.info] network
unreachable resolving 'L.ROOT-SERVERS.NET//IN': 2001:500:2f::f#53
The config files are below, we are running BIND 9 on Solaris 10. We
currently have 2 domain names configured and on IP address on the BIND
server itself. Any ideas from the gurus??
Thanks
cat named.conf
options {
directory "/var/named";
};
zone "0.0.127.in-addr.arpa" {
type master;
file "db.127.0.0";
};
zone "test.local" {
type master;
file "db.test";
};
zone "test2.local" {
type master;
file "db.test2";
};
zone "118.10.10.in-addr.arpa" {
type master;
file "db.10.10.118";
};
zone "119.10.10.in-addr.arpa" {
type master;
file "db.10.10.119";
};
zone "240.100.10.in-addr.arpa" {
type master;
file "db.10.1.240";
};
cat db.test
$TTL 86400
@ SOA jedi root ( 1 10800 3600 604800 600 )
NS jedi
localhost A 127.0.0.1
test-scanA 10.10.119.140
A 10.10.119.141
A 10.10.119.142
MX 10 test-scan
dns1A 10.1.240.24
MX 10 dns1
dns2A 10.1.240.23
MX 10 dns2
cat db.test2
$TTL 86400
@ SOA jedi root ( 1 10800 3600 604800 600 )
NS jedi
localhost A 127.0.0.1
test2-scan A 10.10.118.140
A 10.10.118.141
A 10.10.118.142
MX 10 test2-scan
dns1A 10.1.240.24
MX 10 dns1
dns2A 10.1.240.23
MX 10 dns2
___
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
Re: strange (to me) dns resolution problem
> > Am 23.06.2010 22:01, schrieb Hoover Chan: > > > I have a strange problem where most things are working (i.e. I can > > query and get the correct answers from DNS) but a few domains which > > worked before have stopped working. Yet, when I go to another DNS > > server, they do get resolved. > > > > > > Any pointer to where I should look first? Get a newer list of root > > name servers? > > > > > > Thanks in advance. > - "Toto" wrote: > > It would be helpful to have some more details (Bind version used, > > configuration, failing fqdn, ...) On 24.06.10 09:29, Hoover Chan wrote: > The machine in question is running bind 9.2.1. There is your problem. You should upgrade to at least 9.4. If you want better answer, you must provide more information than just the firsst one. And, please, configure your mailer to wrap lines below 80 characters per line. 72 to 75 is usually OK. -- Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/ Warning: I wish NOT to receive e-mail advertising to this address. Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu. Support bacteria - they're the only culture some people have. ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: strange (to me) dns resolution problem
The machine in question is running bind 9.2.1. Thanks. - Hoover Chanhc...@mail.ewind.com -or- hc...@well.com Eastwind Associates P.O. Box 16646 voice: 415-731-6019 -or- 415-565-8936 San Francisco, CA 94116 - "Toto" wrote: > Am 23.06.2010 22:01, schrieb Hoover Chan: > > I have a strange problem where most things are working (i.e. I can > query and get the correct answers from DNS) but a few domains which > worked before have stopped working. Yet, when I go to another DNS > server, they do get resolved. > > > > Any pointer to where I should look first? Get a newer list of root > name servers? > > > > Thanks in advance. > > > > > > It would be helpful to have some more details (Bind version used, > configuration, failing fqdn, ...) > > > Ciao > Toto ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: strange (to me) dns resolution problem
Am 23.06.2010 22:01, schrieb Hoover Chan: I have a strange problem where most things are working (i.e. I can query and get the correct answers from DNS) but a few domains which worked before have stopped working. Yet, when I go to another DNS server, they do get resolved. Any pointer to where I should look first? Get a newer list of root name servers? Thanks in advance. It would be helpful to have some more details (Bind version used, configuration, failing fqdn, ...) Ciao Toto ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
strange (to me) dns resolution problem
I have a strange problem where most things are working (i.e. I can query and get the correct answers from DNS) but a few domains which worked before have stopped working. Yet, when I go to another DNS server, they do get resolved. Any pointer to where I should look first? Get a newer list of root name servers? Thanks in advance. - Hoover Chanhc...@mail.ewind.com -or- hc...@well.com Eastwind Associates P.O. Box 16646 voice: 415-731-6019 -or- 415-565-8936 San Francisco, CA 94116 ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
