Hello.
Before apply the updates of Redhat9 I had several problems with BIND too,did
you applied the updates? Mainly you need glibc updates.
Josep
El Lunes 02 Junio 2003 20:50, Paul Shepherd escribió:
> Hi,
>
> I have recently started to learn about Linux and have installed RH9 on an
> old PC and I'm having problems getting BIND v9.2.1 to work.
>
> Named is configured as a simply caching nameserver. With named running,
> when I use dig for addresses in domains such as .uk .fr and .de seem to
> resolve correctly while others such as .com .org .net etc do not:
>
> [EMAIL PROTECTED] named]# dig bbc.co.uk
> ; <<>> DiG 9.2.1 <<>> bbc.co.uk
> ;; global options: printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30302
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;bbc.co.uk. IN A
>
> ;; ANSWER SECTION:
> bbc.co.uk. 900 IN A 132.185.132.204
>
> ;; AUTHORITY SECTION:
> bbc.co.uk. 900 IN NS ns1.bbc.co.uk.
> bbc.co.uk. 900 IN NS ns1.thdo.bbc.co.uk.
> bbc.co.uk. 900 IN NS ns1.thny.bbc.co.uk.
> bbc.co.uk. 900 IN NS ns.bbc.co.uk.
>
> ;; Query time: 180 msec
> ;; SERVER: 127.0.0.1#53(127.0.0.1)
> ;; WHEN: Sun Jun 1 22:11:17 2003
> ;; MSG SIZE rcvd: 124
>
> [EMAIL PROTECTED] paul]# dig ibm.com
> ; <<>> DiG 9.2.1 <<>> ibm.com
> ;; global options: printcmd
> ;; connection timed out; no servers could be reached
> [EMAIL PROTECTED] paul]#
>
> I have tried increasing the timeout ( dig +time=10 ibm.com ) but the result
> is the same.
>
> Key named files are as follows:
>
> =================================================
> named.conf
>
> // generated by named-bootconf.pl
>
> options {
> directory "/var/named";
> query-source address * port 53;
> };
>
> //
> // a caching only nameserver config
> //
> controls {
> inet 127.0.0.1 allow { localhost; } keys { rndckey; };
> };
> zone "." IN {
> type hint;
> file "named.ca";
> };
>
> //local loopback
> zone "0.0.127.in-addr.arpa" IN {
> type master;
> file "named.local";
> // allow-update { none; };
> };
> //ip to name mapping
> zone "1.168.192.in-addr.arpa" IN {
> type master;
> file "db.1.168.192.in-addr.arpa";
> allow-update { none; };
> };
>
> include "/etc/rndc.key";
>
> =================================================
> named.local
>
> $TTL 86400
> @ IN SOA localhost. root.localhost. (
> 1 ; Serial
> 3h ; Refresh
> 1h ; Retry
> 1w ; Expire
> 1h ) ; Minimum
>
> IN NS localhost.
>
> 1 IN PTR localhost.
>
>
> =================================================
> db.1.168.192.in-addr.arpa
>
> $TTL 86400
> @ IN SOA localhost. root.localhost (
> 5 ; serial
> 28800 ; refresh
> 7200 ; retry
> 604800 ; expire
> 86400 ; ttk
> )
>
> @ IN NS xps.
>
> 1 IN PTR st530.
> 2 IN PTR Inspiron.
> 3 IN PTR Dell4100.
> 4 IN PTR xps.
>
> =================================================
> resolv.conf
>
> nameserver 127.0.0.1
>
> =================================================
>
> The Linux PC is running on a small network with an adsl
> modem/router/firewall (Alcatel st530). TCP and UDP ports 53 are open. If
> PCs point at the gateway for DNS resolution then all domain names are
> resolved.
>
> I have read the various how-to's and borrowed the O'Reilly book but can't
> find any information as to what may be the cause.
>
> Any suggestions?
>
> TIA
>
> Paul Shepherd
--
redhat-list mailing list
unsubscribe mailto:[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/redhat-list
