[opensuse] HUmm nothing is as simple as it used to be DNS server 11.3
Hi once again ..! I need to get a working DNS server on an internal network port that has absolutely zero effect at all on a wlan connection (just happens to be my outside connection and gets it's ip from the wireless router) the ethernet port i want to hang my NAS device off needs to have a dns server on it . now on 10.1 this was an absolute whiz simple as you like but now 11.3 Oh boy how the heck does one setup a dns on 11.3 that talks to eth0 only with a base address of 192.168.1.1 it must have no effect at all on wlan0 Pete . -- Powered by openSUSE 11.3 (x86_64) Kernel: 2.6.34.7-0.5-desktop KDE Development Platform: 4.4.4 (KDE 4.4.4) "release 3" 17:44 up 1:27, 6 users, load average: 0.71, 0.77, 0.83 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Peter Nikolic wrote:
Hi once again ..!
I need to get a working DNS server on an internal network port that has absolutely zero effect at all on a wlan connection (just happens to be my outside connection and gets it's ip from the wireless router)
the ethernet port i want to hang my NAS device off needs to have a dns server on it . now on 10.1 this was an absolute whiz simple as you like but now 11.3 Oh boy how the heck does one setup a dns on 11.3 that talks to eth0 only with a base address of 192.168.1.1
it must have no effect at all on wlan0
Pete .
Try dnsmasq. It's easy to set up. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wed, 2010-12-08 at 16:02 -0500, James Knott wrote:
Peter Nikolic wrote:
Hi once again ..! I need to get a working DNS server on an internal network port that has absolutely zero effect at all on a wlan connection (just happens to be my outside connection and gets it's ip from the wireless router) the ethernet port i want to hang my NAS device off needs to have a dns server on it . now on 10.1 this was an absolute whiz simple as you like but now 11.3 Oh boy how the heck does one setup a dns on 11.3 that talks to eth0 only with a base address of 192.168.1.1
In /etc/named.conf specify a "listen" directive? Like "listen-on { 192.168.1.1; };" The default is "listen-on { any; };" http://www.cyberciti.biz/faq/unix-linux-bsd-bind-dns-listenon-configuration/
it must have no effect at all on wlan0
I don't understand what this means - running a service has "no effect at all" on an *interface*. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 12/08/2010 11:49 AM, Peter Nikolic wrote:
Hi once again ..!
I need to get a working DNS server on an internal network port that has absolutely zero effect at all on a wlan connection (just happens to be my outside connection and gets it's ip from the wireless router)
the ethernet port i want to hang my NAS device off needs to have a dns server on it . now on 10.1 this was an absolute whiz simple as you like but now 11.3 Oh boy how the heck does one setup a dns on 11.3 that talks to eth0 only with a base address of 192.168.1.1
it must have no effect at all on wlan0
Pete .
Uuhg.. dunno? I would tell you to let bind provide addresses for both wired and wireless. I've never had reason to do one but not the other. I always figured it was better to have name resolution handled in one spot for the whole subnet. I can't say enough about the relatively painless setup of bind configured to receive dynamic updates from dhcpd using t-sig keys. You then have one central dns mechanism and can use dhcpd.conf for fine grain control of the address space. Generally, the only tweaks that I do other than separating the fixed/dynamic address ranges it to assign specific fixed addresses to hosts based on mac addresses that lets me guarantee that a specific box gets a specific address handed out when they show up on the network. e.g.: host Rankin-P35a.3111skyline.com { hardware ethernet 00:11:f5:15:2d:83; fixed-address 192.168.6.101; } guarantees my old Tosh laptop gets .101 assigned even though it is coming in over a wireless link while: host killerz.3111skyline.com { hardware ethernet 00:21:85:14:F0:FE; fixed-address 192.168.6.106; } my son's box gets 106 coming in over a wired link. Is there any reason you couldn't use a standard setup like that? If so, you could set it up once and then just forget about it for years..... It just keeps working. -- David C. Rankin, J.D.,P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thursday 09 Dec 2010 08:55:42 David C. Rankin wrote:
On 12/08/2010 11:49 AM, Peter Nikolic wrote:
Hi once again ..!
I need to get a working DNS server on an internal network port that has absolutely zero effect at all on a wlan connection (just happens to be my outside connection and gets it's ip from the wireless router)
the ethernet port i want to hang my NAS device off needs to have a dns server on it . now on 10.1 this was an absolute whiz simple as you like but now 11.3 Oh boy how the heck does one setup a dns on 11.3 that talks to eth0 only with a base address of 192.168.1.1
it must have no effect at all on wlan0
Pete .
Uuhg.. dunno?
I would tell you to let bind provide addresses for both wired and wireless. I've never had reason to do one but not the other. I always figured it was better to have name resolution handled in one spot for the whole subnet. I can't say enough about the relatively painless setup of bind configured to receive dynamic updates from dhcpd using t-sig keys.
You then have one central dns mechanism and can use dhcpd.conf for fine grain control of the address space. Generally, the only tweaks that I do other than separating the fixed/dynamic address ranges it to assign specific fixed addresses to hosts based on mac addresses that lets me guarantee that a specific box gets a specific address handed out when they show up on the network. e.g.:
host Rankin-P35a.3111skyline.com { hardware ethernet 00:11:f5:15:2d:83; fixed-address 192.168.6.101; }
guarantees my old Tosh laptop gets .101 assigned even though it is coming in over a wireless link while:
host killerz.3111skyline.com { hardware ethernet 00:21:85:14:F0:FE; fixed-address 192.168.6.106; }
my son's box gets 106 coming in over a wired link.
Is there any reason you couldn't use a standard setup like that? If so, you could set it up once and then just forget about it for years..... It just keeps working.
Hi David .. Nope cant let anything touch wlan0 that gets it's ip from another source it is my incoming connection and works fine . I have got dnsmasq working now the docs are not too clear but once sorted it is fine .. I did look at bind but the first thing it did was went straight for the wireless so it got the chop no can do .. Cheers Pete .. -- Powered by openSUSE 11.3 (x86_64) Kernel: 2.6.34.7-0.5-desktop KDE Development Platform: 4.4.4 (KDE 4.4.4) "release 3" 10:33 up 18:15, 5 users, load average: 0.77, 0.44, 0.18 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Peter Nikolic wrote:
I did look at bind but the first thing it did was went straight for the wireless so it got the chop no can do ..
Yes, the default for bind is to listen on all interfaces. IT is configurable though. -- Per Jessen, Zürich (2.3°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Thu, 2010-12-09 at 12:25 +0100, Per Jessen wrote:
Peter Nikolic wrote:
I did look at bind but the first thing it did was went straight for the wireless so it got the chop no can do .. Yes, the default for bind is to listen on all interfaces. IT is configurable though.
Which was explained in this thread yesterday listen-on { 192.168.1.1; }; Solves the problem. Default is listen-on { any; }; Which is perfectly reasonable. *Still* having bind *listen* on wlan0 will not effect anything-at-all unless something tells somebody to use the resolver on that address. Just running a resolver on that interface won't do anything - and if it is your external interface the firewall configuration probably blocks all ingress traffic anyway. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (5)
-
Adam Tauno Williams -
David C. Rankin -
James Knott -
Per Jessen -
Peter Nikolic