Be DNS need change

Be router DNS address should change before 31st January 2010 on WAN1

Be DNS IP address change

Hi Members,

At the end of 2008, we upgraded our DNS servers to make them faster and more reliable. At the end of January 2010, we're going to turn the old ones off. We migrated most members to the new servers over the course of the year. Due to the configuration of your modem, however, you are among a small group who are still using the old DNS servers.

This means that on 31st January you will lose the ability to surf the web. Crikey!

But keep reading because there are things that we can help you do if you are using a BE Box. The options get more and more technical as you read, so pick the one you're most comfortable with.

The new server everyone needs to use is 87.194.255.154

Option 1: The Wizard

The easiest way to change your DNS setting is to run the set-up wizard again (this is the tool you used to set up your Static IP).
You can access a guide to the wizard here: https://www.bethere.co.uk/web/beportal/techguides_changing_dns_settings_via_bebox_wizard


The drawback to this method is that you will lose any personalised setting (like port forwards or customised wireless settings).

Option 2: Dr. Sox's Multifunctional Tool

DrSox of the BE Usergroup has developed a tool that is capable of many things.one of them being to update your BE Box DNS settings without losing your personalised settings.

Here's where you can find the program and the guide: www.bethere.co.uk/web/beportal/techguides_changing_dns_settings_using_usergroup_tool

Option 3: The CLI

The usergroup site hosts a guide to changing your DNS settings via the CLI. If you don't know what that means, best not try it. Unless you're brave.

Here's the usergroup page: http://www.beusergroup.co.uk/technotes/index.php/OpenDNS

Remember to use 87.194.255.154

Need Advice?

We've got all our support channels available to you. For some great technical advice, visit one of the following:

-Chat with staff, the usergroup and other BE members

-Forum (access via the member centre)

-Raise a ticket or live chat with an agent from your account

-Call us on 0808 101 3430

All the best -

Everyone @BE

BT Line Install & Be CXStaffcall2 line Disconnect

Today 6/5/2009 I have been to CharingX Golding House.

WAN2 connection from Be ADSL line CXStaffcall2 completely disconnected by request from MICK.
BT activated old line (Phone No: 020 3184 0091) with different IP Range and supplied a BT Business Hub. I have removed Draytek 2820 router replaced with BT Hub and reconfigured WAN4.

BT HUB Router IP address: 217.34.5.62
WAN4: IP address: 217.34.5.49 Mask: 255.255.255.240
Usable IP range: 217.34.5.49 to 217.34.5.61 (13 IP address)

Initially only activated and given 100% traffic to WAN4 on load balance then connected my laptop in to LAN. Internet was worked fine. That proved new BT line was working via WAN4.

Then I have set the load balance on WAN1: 40%, WAN3: 30% and WAN4: 30%.
Then made a back up of the current configuration om my LAPTOP.

I made sure Internet was working on LAN by connecting my LAP TOP.

Returned to office and tested VPN connections. WAN1, WAN3 and WAN4 VPN connections were working fine and I able to log in Draytek load balance via these VPN connections.

In at CX with Kugan, (WAN1 & WAN3 connected) ping times 16-36mSec.
WAN4 not

BT ceased WAN4 on 25th Feb. Not re-ordered line.
Was Option 2 broadband no contention ratio no more than 10 PC's, £25 + static IP +£10
should be Network Broadsband 20:1 (best one) £58.50/month

Will take 5 days, By next Wednesday, activated by 8.00pm
In case of problems call 0845 600 7020 - I told him this line comes up NU!!!!
0800 1698 639 option 9 twice.

System checked OK, ping times to google 61-76mSec

Mick Rang,
CX down, WAN2 (LB can't check its status) had failed. I restarted the LB without WAN2 (Just WAN1 & WAN3).

System running OK, Loadbalancing WAN1,2,3 40%,40%,20%. Ping times nearly half a second. Not many timeouts.

Loadbalancer check shows WAN1 disconnected again (even though there is dial tone). System running on WAN3 only. Yesterday I had put a line test on WAN1 to ping www.google.co.uk to knock it out if it failed.

Power cycled WAN1, it reconnected at 6.5Mbps, but the throughput was low. I figured this might be due to the auto weighting on the loadbalancing, set it to 70% adsl, 30% sdsl and rebooted.

WAN1 was downloading about 3000 packets every 10 sec.

Whilst I was on site, I noticed WAN2 link total fail, return, totaly fail return etc.

Disabled NTP on WAN2 router as this had never updated.

Updated software in AR440S WAN1 and WAN2 as there was an update the the adsl code.
WAN1 connected 6.5Mbps. WAN2 connected 7.1Mbps.
Set Loadbalancer to autoweight loadbalance over 4 lines (hoping WAN4 will soon get re-instated). WAN2 traffic very small.
WAN2

10/3/2009 Tue evening.

I had left the system earlier in the day loadbalancing WAN2 and WAN3. (WAN1 had no dial tone).
Evening check showed WAN2 failed (again) but WAN1 back again.

Reconfigured the system to Loadbalance WAN1 and WAN3.

Mark Mollison called saying the staff Internet was down at CX.

I could log in with PPTP on WAN1 and on WAN3. Not WAN2.

On arrival at CX, the WAN1 and WAN2 ADSL lights indicated lines up, but checking with phone reciver:
020 8741 0055 working (staffcall2) WAN2
020 8741 0925 no dial tone (staffcall1) WAN1 (note discrepancy)

I called Be, they said I have to call BT 150 as there is a voice fault on the line.
BT said fix by Wed 11th March 6pm worst case - Fault Ref LW8DRJ87.
Note: because of the way Be set up these lines (same gateway address) the loadbalancer can not shut down one of these lines in case of a fault.

Phoned BT re WAN4 (Draytek) not working Cease order on 020 3184 0091 (25/2/2009).
Loadbalancer had detected failure & knocked this one out of Loadbalancing when it was ceased.

Logged into WAN2, (analog line OK) got lots of: Internal Error: speed mismatch causing transmit internal rate underrun error.
Console port showed line connected at 3.5Meg download, but could not get ethernet connection.
Reset AR440S router, it reconnected at 7Meg, and could get ethernet connection.

Set Loadbalancer to balance WAN2 & 3, left site with system working OK.