Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Technicolor 582 DHCP Domain Name
99 views
Skip to first unread message
Geoff Clements
Jun 14, 2012, 3:50:29 PM6/14/12
to
Problem:
I use my Technicolor 582 router the a DHCP serveron my A&A supplied sub-net.
Whenever a client obtains an IP address it also receives a domain name of
"lan" from the router. I've looked through both the web interface for the
router and the telnet commands but I cannot find where this can be changed.
Anyone else know?
Background:
I'm trying to set up web proxy auto-configuration (WPAD). I've got a
wpad.dat file being served by my web server and tested to be working
correctly by setting Firefox (Iceweasel) to get this file with a manual
config. entry. I'd like to get rid of the manual entry and use the built-in
WPAD of Firefox.
To do this Firefox will examine what domain name is being used and try to
resolve wpad.domainname (actually it's a bit more complicated but that's the
basics). So in my case FF is sending out DNS requests to resolve wpad.lan
which can't be resolved. I have already set up a DNS entry to the correct
location and tested this. I'd really like my clients to the the true domain
name at DHCP config time.
Geoff
I use my Technicolor 582 router the a DHCP serveron my A&A supplied sub-net.
Whenever a client obtains an IP address it also receives a domain name of
"lan" from the router. I've looked through both the web interface for the
router and the telnet commands but I cannot find where this can be changed.
Anyone else know?
Background:
I'm trying to set up web proxy auto-configuration (WPAD). I've got a
wpad.dat file being served by my web server and tested to be working
correctly by setting Firefox (Iceweasel) to get this file with a manual
config. entry. I'd like to get rid of the manual entry and use the built-in
WPAD of Firefox.
To do this Firefox will examine what domain name is being used and try to
resolve wpad.domainname (actually it's a bit more complicated but that's the
basics). So in my case FF is sending out DNS requests to resolve wpad.lan
which can't be resolved. I have already set up a DNS entry to the correct
location and tested this. I'd really like my clients to the the true domain
name at DHCP config time.
Geoff
Geoff Clements
Jun 15, 2012, 4:44:57 PM6/15/12
to
Geoff Clements wrote:
> Problem:
>
> I use my Technicolor 582 router the a DHCP serveron my A&A supplied
> sub-net. Whenever a client obtains an IP address it also receives a domain
> name of "lan" from the router. I've looked through both the web interface
> for the router and the telnet commands but I cannot find where this can be
> changed. Anyone else know?
>
I've made a little progress, the telnet command to change the domain name
> Problem:
>
> I use my Technicolor 582 router the a DHCP serveron my A&A supplied
> sub-net. Whenever a client obtains an IP address it also receives a domain
> name of "lan" from the router. I've looked through both the web interface
> for the router and the telnet commands but I cannot find where this can be
> changed. Anyone else know?
>
is:
dns server config domain=<domain name>
and when I do this Firefox does a correct DNS query for the wpad.dat file.
Unfortunately when I do this I can no longer resolve addresses to my domain
(except for those in the /etc/hosts file) ... grrr!
I guess this may be because the command above sets the router to be the
authoritative DNS server for my domain?
--
Geoff
Geoff Clements
Jun 25, 2012, 8:38:03 AM6/25/12
to
Just a quick follow up.
After some faffing around with the Technicolor I couldn't find a way to make it return the correct domain name via DHCP _and_ correctly serve DNS queries for my domain at the same time, clearly this is too much for its tiny brain.
So I ended up side-stepping the issue by switching off DHCP at the router and installing dnsmasq on my server. At least this gives me full control over DHCP and has the extra benefit of making host names resolvable on my network. On top of that automatic WPAD file detection works great.
After some faffing around with the Technicolor I couldn't find a way to make it return the correct domain name via DHCP _and_ correctly serve DNS queries for my domain at the same time, clearly this is too much for its tiny brain.
So I ended up side-stepping the issue by switching off DHCP at the router and installing dnsmasq on my server. At least this gives me full control over DHCP and has the extra benefit of making host names resolvable on my network. On top of that automatic WPAD file detection works great.
0 new messages