Re: BIND Configuration


Yes, dns-server itself seems to work very well. when I query some public
domains - google.com, yahoo.com -, the result is fine.
but when I put zone files to /etc/namedb/named.conf, the domain is not
resolved.

What is your search path (resolv.conf)? Note dhclient.conf
controls this if you get your addresses via dhcp.

One more thing, /etc/resolv.conf is changed whenever the server reboot
because the server get dynamic IP from ISP.

Assuming DHCP look at dhclient.conf.

e.g.

interface "sis0" {
supersede domain-name "dv.isc.org isc.org";
prepend domain-name-servers 127.0.0.1;
}

On 6/28/07, ait ^__~ <ait.meijin@xxxxxxxxx> wrote:

If iget it correct - name resolving don't work at all. Is name resolving
works on dns-server itself? Maybe you want to check configs in your
/etc/resolv.conf file on your dns-server.

2007/6/29, Minseok Choi <eraser95@xxxxxxxxx>:

Hi, I am digging on how to make home server.
The home server is for Wireless AP, file server, samba and LAMP.
The current progress is almost done but I can't solve this problem so
far.

I have 3 PCs. One is home server and the others(A, B) are WinXP.
I have to know A's IP to access A because WinXP got dynamic IP from the
Home
Server.

Is there any way to assign real name instead of IP. I am trying to use
BIND
like the below.
After the configuration, nslookup said the names - bellevue, issaquah
and
sammanish - can't be found.
I'd merely like to access PCs using real name. If you have any idea or
information, please let me know.

----------------------------------------
/etc/named.conf

zone "intranet" {
type master;
file "master/intranet.zone"
}

zone "0.168.192.IN-ADDR.ARPA" {
type master;
file "master/intranet.rev"
}
----------------------------------------
/etc/master/intranet.zone
@ IN SOA localhost. root.localhost. (
20070628 ; Serial
3600 ; Refresh
900 ; Retry
3600000 ; Expire
3600 ) ; Minimum
IN NS localhost.
bellevue IN A 192.168.0.1
issaquah IN A 192.168.0.2
sammamish IN A 192.168.0.3

----------------------------------------
/etc/master/intranet.rev

$TTL 3600

@ IN SOA localhost. root.localhost . (
20070628 ; Serial
3600 ; Refresh
900 ; Retry
3600000 ; Expire
3600 ) ; Minimum
IN NS localhost.
1 IN PTR bellevue.
2 IN PTR issaquah.
3 IN PTR sammamish.

These should be "bellevue.intranet", etc.

_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx
"



_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark_Andrews@xxxxxxx
_______________________________________________
freebsd-stable@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: BIND9 Latency
    ... it times out when resolving Internet ... Have you specified a forwarding name server in the /etc/named.conf ... forwards, and zone synchronisation. ...
    (Ubuntu)
  • Re: DNS Domain name question
    ... Changing the DNS ... Then you are going to create a private zone that is NOT within their ... I do not control the Unix boxes so they will be resolving ... This is NOT an issue IF the parent zone will delegate. ...
    (microsoft.public.win2000.dns)
  • Re: DNS Issue on Windows 2003 Server
    ... You said there were no records in the zone pointing the url to an external ... the dns query may be getting forwarded to one of your root hints and ... DNS is resolving the address to an ... >>> using this DNS Server cannot connect to Yahoo Mail? ...
    (microsoft.public.windows.server.dns)
  • Bind9.3 Bug?
    ... zone "224-239.xxx.xxx.xxx.in-addr.arpa" { ... cause when setting allow-query; globally then resolving from ... a other bind9.3 resolver will work but from a bind8 resolver it wont... ... with this configuration all recursiv lookups worked from everywhere, ...
    (freebsd-current)