Telecom 2Wire Router DNS problem with apple laptop?

Forums › LAN (ethernet/Wifi/routers/Bluetooth) › Telecom 2Wire Router DNS problem with apple laptop?

stw

64 posts

Master Geek

#96248 23-Jan-2012 12:16

Im just setting up a new router I got from telecom 2Wire router.

Its connected to the internet my Skype works fine but I had to manually put in telecoms DNS settings into my computer (Apple Mac) so I could browse the net.

My iPhone connects to the wife but the internet doesn't work!!

There seems to be a problem with the DNS settings on the router but when I log onto the router it appear to have the right DNS settings.

Has any had this same problem and how do I fix it? I don't want to have to manually put in DNS setting on every computer.

Hammerer

2476 posts

Uber Geek

Lifetime subscriber

#572376 23-Jan-2012 14:36

Is there a problem with your DHCP (Dynamic Host Configuration Protocol) configuration? For example, it might be turned off at the router if more than one device can't connect to the Internet.

DHCP assigns an IP address to your computer/phone/ etc and assigns other network parameters including the DNS name servers.

krt

2 posts

Wannabe Geek

#572391 23-Jan-2012 15:06

hey I checked his settings, the router is faulty.

dhcp is working fine. these routers work out of the box. have done a factory reset and double checked that dncp is on, client gets dhcp address fine.

oddly enough, can see the router is picking up the correct DNS from Telecom
Primary DNS: 202.27.158.40
Secondary DNS: 202.27.156.72

on the client can see via DHCP its using the routers IP for the DNS (192.168.1.254) but client cant resolve anything. if manually specify dns server on client e.g. 202.27.158.40 it works fine.

even tried manually specifying DNS on router but doesn't make any difference

new one is it the way

stw

64 posts

Master Geek

#573123 25-Jan-2012 11:18

I got a brand new 2Wire router today and still have same problem!!!!

webwat

2036 posts

Uber Geek

Trusted

#573290 25-Jan-2012 20:54

Is the router supposed to allocate the 2wire.net domain with DHCP? Anyway, you might be able to find a setting for DNS proxy/forwarding that you can change.

Time to find a new industry!

greenleader

5 posts

Wannabe Geek

#575993 1-Feb-2012 17:07

+1 Exact same problem. Can connect to net if I hard code the Telecom DNS settings but that doesn't work for iPhone and iPad. The 2Wires is brand new out of the box. Did a new router resolve the problem?

greenleader

5 posts

Wannabe Geek

#576676 3-Feb-2012 09:43

Bump..... anyone got any ideas?

networkn

Networkn
32358 posts

Uber Geek

ID Verified

Trusted

Lifetime subscriber

#576680 3-Feb-2012 09:50

Yes I had this problem with a customer, turned out to be a MTU (can't recall but it was set to something bigger than it should have been) problem, they couldn't fix it in the end and supplied an alternative brand for them.

Quic Broadband

Move to New Zealand's best fibre broadband service (affiliate link). Free setup code: R587125ERQ6VE. Note that to use Quic Broadband you must be comfortable with configuring your own router.

greenleader

5 posts

Wannabe Geek

#576696 3-Feb-2012 10:34

I read somewhere that changing the MTU to 1492 may fix it. That makes no sense to me but your experience would seem to support an MTU issue. I will look to change it and report back. Any other thoughts much appreciated. I guess plan B is to get Telecom to replace it. Cheers...Andrew

greenleader

5 posts

Wannabe Geek

#577657 5-Feb-2012 21:04

I'm due on site Tuesday to try and fix this issue. I have got things going in the meantime by changing the iPhone (and iPad) over to Static Addressing and adding Telecoms primary DNS IP Address. But this is not the way it should be and I'd really love to crack it rather than just admit defeat, blame Telecom and try and get a different brand router out of them. Any advice or ideas that I could try would be greatly appreciated.

greenleader

5 posts

Wannabe Geek

#582561 16-Feb-2012 21:26

Anyone got any updates on this. I'm assuming replacing the router is still the best plan.

coffeenow

33 posts

Geek

ID Verified

Trusted

#638104 9-Jun-2012 01:32

Replacing the router best plan if you're using Macs...

According to the Telecom broadband helpdesk it's a fault in the latest 2Wire router firmware that causes DNS problems with Macs. They suggested the router be swapped for another Telecom router (Technica (?) or Thompson).

I experienced exactly the same issues with a 2Wire ADSL wireless router supplied by Telecom for testing.

- The router connected to the internet and successfully received valid IP and DNS settings
- All devices connected to the router via wifi and received valid IP and DNS settings (pointing to router)
- MacBook Pro and iPhones could not connect to the internet but iMac could (all on wifi)
- MacBook Pro could connect to internet when Mac DNS set to OpenDNS (using DNSCrypt)

Conclusion: DNS requests from MacBook Pros and iPhones are passed to router but fail to reach external DNS. Telecom have observed this fault with Macs since the latest 2Wire firmware update (they mentioned that this fault may not be known by all helpdesk staff).

krt

2 posts

Wannabe Geek

#638113 9-Jun-2012 07:17

I found a fix to this awhile ago.

The problem is the Telecom 2Wire gateway doesnt seem to work as a DNS server for Apple Mac computers or even iPhone, iPad etc.

You can login to the modem and configure it to provide the Telecom DNS servers directly to the client.

This is how you fix it:

Go to modem webpage: http://192.168.1.254
Click Settings
Select Link Configuration
The default password: admin

Now go down to DNS and adjust it to "Manually Specify DNS information"
Primary server: 202.27.158.40
Secondary server: 202.27.156.72

Save it and your done!

coffeenow

33 posts

Geek

ID Verified

Trusted

#638135 9-Jun-2012 09:34

Thanks for that workaround. I can't confirm it as the client has returned the router but hopefully it works for someone with this issue.

N.B. 1) The router does configure the correct Telecom DNS values automatically. 2) I did try manually configuring the router to point to OpenDNS but it didn't appear to fix the issue.