DNS servers routing error?
I'm connected to a gateway in Telehouse East, so why am I going through the load balancers in City Lifeline to get to the DNS servers?
C:\Documents and Settings\John>tracert 212.159.6.9
Tracing route to cdns01.plus.net [212.159.6.9]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dg834 [192.168.0.1]
2 19 ms 15 ms 14 ms lo0-homesurf.pte-ag2.plus.net [195.166.128.73]
3 22 ms 22 ms 15 ms ge0-0-0-505.pte-gw1.plus.net [84.92.4.97]
4 29 ms 23 ms 15 ms te2-2.pcl-gw01.plus.net [212.159.0.185]
5 27 ms 21 ms 50 ms vl63.pcl-lb01.plus.net [212.159.2.252]
6 25 ms 42 ms 16 ms cdns01.plus.net [212.159.6.9]
Trace complete.
C:\Documents and Settings\John>tracert 212.159.6.10
Tracing route to cdns02.plus.net [212.159.6.10]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dg834 [192.168.0.1]
2 14 ms 14 ms 14 ms lo0-homesurf.pte-ag2.plus.net [195.166.128.73]
3 12 ms 12 ms 13 ms ge0-0-0-505.pte-gw1.plus.net [84.92.4.97]
4 19 ms 16 ms 16 ms te2-2.pcl-gw01.plus.net [212.159.0.185]
5 13 ms 17 ms 16 ms vl63.pcl-lb01.plus.net [212.159.2.252]
6 18 ms 13 ms 15 ms cdns02.plus.net [212.159.6.10]
Trace complete.
C:\Documents and Settings\John>tracert 212.159.13.49
Tracing route to cdns01.plus.net [212.159.13.49]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dg834 [192.168.0.1]
2 27 ms 17 ms 40 ms lo0-homesurf.pte-ag2.plus.net [195.166.128.73]
3 35 ms 37 ms 16 ms ge0-0-0-505.pte-gw1.plus.net [84.92.4.97]
4 12 ms 12 ms 13 ms te2-2.pcl-gw01.plus.net [212.159.0.185]
5 139 ms 34 ms 15 ms vl63.pcl-lb01.plus.net [212.159.2.252]
6 44 ms 42 ms 29 ms cdns01.plus.net [212.159.13.49]
Trace complete.
C:\Documents and Settings\John>tracert 212.159.13.50
Tracing route to cdns02.plus.net [212.159.13.50]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms dg834 [192.168.0.1]
2 73 ms 79 ms 31 ms lo0-homesurf.pte-ag2.plus.net [195.166.128.73]
3 65 ms 55 ms 73 ms ge0-0-0-505.pte-gw1.plus.net [84.92.4.97]
4 20 ms 17 ms 50 ms te2-2.pcl-gw01.plus.net [212.159.0.185]
5 25 ms 29 ms 50 ms vl63.pcl-lb01.plus.net [212.159.2.252]
6 34 ms 17 ms 93 ms cdns02.plus.net [212.159.13.50]
Trace complete.
Probably because pte-ag2 (or at least the gateway pte-ag2 with IP 195.166.128.72) only has access to DNS servers at PCL. All roads lead to Rome and all that.
If you were on a THN gateway then you'd be finding you only had access to DNS servers at PTN and again, all roads lead to Rome.
If, however, you were on pte-ag1 then you'd be *very* lucky and find that you actually did have the choice of primary and secondary DNS servers where one was at PCL and the other was at PTN.
I'm not sure about the relevance of your particular gateway IP being 195.166.128.73 tho as I haven't come across that one before. Maybe you were expecting and would normally be getting something different to the tracerts you posted ? although they do look exactly "as expected" to me.
Please note that all my comments above are made based on the partial network/routing diagram that I've been drawing for several weeks/months now but PN may possibly have tweaked things a bit since I started so my info may be out of date.
I posted something quite some time ago about this and in particular questioning the benefit (or lack thereof) of having 2 independent DNS platforms where, with the exception of pte-ag1, only one of which is ever accessible from any gateway and all 'independent' servers are apparently fed from the very same router/balancer. I've no idea if a response has been forthcoming or not by now as I kinda gave up monitoring the thread after a while I'm afraid and I can't even remember which thread it was on now in order to have a quicky looky see
I'll see if I can find the relevant thread later in case there was a response of some sort.
If you were on a THN gateway then you'd be finding you only had access to DNS servers at PTN and again, all roads lead to Rome.
If, however, you were on pte-ag1 then you'd be *very* lucky and find that you actually did have the choice of primary and secondary DNS servers where one was at PCL and the other was at PTN.
I'm not sure about the relevance of your particular gateway IP being 195.166.128.73 tho as I haven't come across that one before. Maybe you were expecting and would normally be getting something different to the tracerts you posted ? although they do look exactly "as expected" to me.
Please note that all my comments above are made based on the partial network/routing diagram that I've been drawing for several weeks/months now but PN may possibly have tweaked things a bit since I started so my info may be out of date.
I posted something quite some time ago about this and in particular questioning the benefit (or lack thereof) of having 2 independent DNS platforms where, with the exception of pte-ag1, only one of which is ever accessible from any gateway and all 'independent' servers are apparently fed from the very same router/balancer. I've no idea if a response has been forthcoming or not by now as I kinda gave up monitoring the thread after a while I'm afraid and I can't even remember which thread it was on now in order to have a quicky looky see
I'll see if I can find the relevant thread later in case there was a response of some sort.
You've got this completely wrong Mike.
AFAIK there are two sets of DNS servers behind load balancers, one in one of the Telehouse datacentres (THN, PTE and PTN) and another in City Lifeline. Both sets of servers present as the four IPs (212.159.6.9, 212.159.6.10, 212.159.13.49 and 212.159.13.50). Actually I believe there are more than four servers behind each load balancer masquarading as those four IPs.
This means that just looking at the last line of a tracert to one of the DNS servers it could be be either in Telehouse or in City Lifeline. You have to look at the line before which is the load balancer to see where the DNS servers are located. E,g. vl63.pcl-lb01.plus.net [212.159.2.252] which is City Lifeline.
I thought the idea was that depending upon your current gateway you hit the nearest DNS servers, so was surprised when connected to a gateway in Telehouse (Docklands) to be using DNS servers in City Lifeline (near Liverpool St).
AFAIK there are two sets of DNS servers behind load balancers, one in one of the Telehouse datacentres (THN, PTE and PTN) and another in City Lifeline. Both sets of servers present as the four IPs (212.159.6.9, 212.159.6.10, 212.159.13.49 and 212.159.13.50). Actually I believe there are more than four servers behind each load balancer masquarading as those four IPs.
This means that just looking at the last line of a tracert to one of the DNS servers it could be be either in Telehouse or in City Lifeline. You have to look at the line before which is the load balancer to see where the DNS servers are located. E,g. vl63.pcl-lb01.plus.net [212.159.2.252] which is City Lifeline.
I thought the idea was that depending upon your current gateway you hit the nearest DNS servers, so was surprised when connected to a gateway in Telehouse (Docklands) to be using DNS servers in City Lifeline (near Liverpool St).
Here's a post from Bob talking about the load balancers: http://community.plus.net/forum/index.php/topic,77567.msg626101.html#msg626101
Read further down that topic for more on this.
Read further down that topic for more on this.
Quote from: jelv AFAIK there are two sets of DNS servers behind load balancers, one in one of the Telehouse datacentres (THN, PTE and PTN) and another in City Lifeline. Both sets of servers present as the four IPs (212.159.6.9, 212.159.6.10, 212.159.13.49 and 212.159.13.50). Actually I believe there are more than four servers behind each load balancer masquarading as those four IPs.
This means that just looking at the last line of a tracert to one of the DNS servers it could be be either in Telehouse or in City Lifeline. You have to look at the line before which is the load balancer to see where the DNS servers are located. E,g. vl63.pcl-lb01.plus.net [212.159.2.252] which is City Lifeline.
That's (almost) exactly what I said above apart from the usage by various gateways ... or at least that's (almost) exactly what I think is the case and what I thought I'd said above anyway !! Sorry if it wasn't as clear as it should have been and all that.
If I could copy the relevant part of the large sheet of paper stuck on the wall in front of me to show you then it would probably be loads clearer. However suffice it to say that all tests indicate that: the following is (or at least WAS) the case when I was working on it::
pcl-* and pte-ag2 ONLY route to 212.159.2.252 (PCL) regardless of destination DNS IP address.
ptn-* and thn-* ONLY route to 212.159.2.124 (PTN) regardless of destination DNS IP address.
pte-ag1 routes to EITHER 212.159.2.252 (PCL) OR 212.159.2.124 (PTN) depending on the destination DNS IP address.
This means that for pte-ag1 (ONLY), 212.159.13.49 and 212.159.6.9 route to PCL and 212.159.13.50 and 212.159.6.10 route to PTN but in all other cases, all connections to all DNS servers are at PCL OR PTN but not both, depending on the gateway being used.
I quite obviously have tracerts from every possible gateway to every possible DNS IP address to back this up if you really want to see them ... but as I said, whilst that clearly WAS the case at the time I was investigating, it is quite possible that it's not strictly speaking the case today of course.
As I said earlier, it seems to me that there are 2 DNS platforms (PCL) and (PTN) but only one of which is ever accessible from any particular gateway with the only exception being pte-ag1 - which has primary DNS on one platform (PCL) and secondary DNS on the other (PTN). All DNS IP addresses (apart from when connected via pte-ag1) are thus behind the same router/balancer in one of 2 places so for any gateway (other than pte-ag1) all roads lead to Rome and there is to all intents and purposes only one DNS server so to speak ! Load balancing does not constitute true redundancy in much the same way that a RAID array doesn't constitute a true backup and all that ... IMHO of course, YMMV
If the situation is still as it was earlier in the year, this suggests that pte-ag1 offers a good level of DNS redundancy/reliability however, the other gateways do not offer anything close to the same level at all.I hope that makes some kind of sense but I'm way more than a tad confused as to why you thought what I said was completely rubbish tho
Unless I'm being particularly stupid or I've missed something of vital importance in what you're saying, then we've both said pretty much exactly the same thing but in different ways I think And I have a certain amount of hard evidence to substantiate my conclusions of course, albeit evidence obtained without the benefit of knowing what exactly I should expect to find or exactly how things are expected to work which is always going to mean a significant possibility of jumping to conclusions rather than looking for any additional evidence there may be 
Maybe if PN produced an up-to-date network/routing diagram as you have requested at least once recently(ish) I think then all would be perfectly clear without having to guess or b*gger around trying to work things out on an ad-hoc basis every time something to aid fault-finding is required
... wanders off to read the linky in case it says anything new
Quote from: Bob That's not strictly true. AFAIK, the routing is calculated using OSPF so will take the shortest path to the DNS servers it can find. If there's a problem with the closest site then traffic should get re-routed to the one that's farther away.
That would be very nice ... but does it ? and perhaps more to the point did it when the PCL DNS platform (or whatever it actually was at PCL) fell over recently ? Apparently not it would seem from my experience because DNS was lost completely from some gateways despite there being another (presumably) fully working DNS platform available at the other site. Other customers had the same experience on other gateways as well I seem to remember so not just me who was 'unlucky' in my choice of gateway and all that. I was on pte-ag2 at the time so it presumably shouldn't have lost DNS completely just because there was some random fault at PCL should it ? It all looked pretty fixed and definitive to me although I don't doubt what you're saying should happen in ideal circumstances of course ... I'm just questioning if it actually does that's all because reality at the time of investigating suggested that DNS is almost certainly not as good as it might be in general under fault conditions and perhaps not even as good as it might be at all for anyone connected via anything other than pte-ag1 at any time.
Maybe you'd also like to check out my rather long collection of tracerts various as well just to back up what I'm saying
although perhaps some of the routes had been OSPF'd of course which is why I saw what I saw at the time I looked, particularly in respect of DNS routing when connected via pte-ag1 Kinda difficult to believe that tho as it all looked pretty consistent and repeatable at the time and may still be so ... but I'm not going to bother finding out.Having said that, if OSPF was implemented and working in all instances then the chances of finding a particular DNS IP that didn't respond would surely be remote and that certainly doesn't seem to be the case in my experience and never has been. It has been common over the years to find my choice of primary DNS occasionally not responding and good old windoze (eventually !) switching to my choice of secondary DNS but that would only ever be required if there were 2 simultaneous failures meaning that the relevant server at both sites was inaccessible or down at the same time wouldn't it ?
Any chance of an updated network/routing diagram and a definitive explanation ?
However, have some tracert p0rN
for the record before I lose it or get round to tidying up at some point in time before someone decides they'd like to see it after all. I think I've extracted all of the relevant data from amongst everything else I still have lying around. I can't remember exactly when they were done but around a month or so ago and quite possibly during the week after Xmas. I could trawl through my logs to look it all up of course but I'm not wasting several hours unless it's *really* important to know exactly when these particular routes existed. I think they were probably done over a day or so TBH although a fair few of the gateways would have been done within minutes of each other. All tracerts on each gateway were definitely done within seconds of each other that's for certain. In addition, numerous random checks made as and when convenient over the following week or so always gave identical results.
1 0 ms 192.168.1.1 Router-adsl
2 16 ms 195.166.128.64 lo0-plusnet.pte-ag1.plus.net
3 16 ms 84.92.4.1 ge0-0-0-403.pte-gw1.plus.net
4 15 ms 212.159.0.185 te2-2.pcl-gw01.plus.net
5 16 ms 212.159.2.252 vl63.pcl-lb01.plus.net
6 15 ms 212.159.13.49 cdns01.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 16 ms 195.166.128.64 lo0-plusnet.pte-ag1.plus.net
3 15 ms 84.92.4.2 ge0-0-0-403.pte-gw2.plus.net
4 32 ms 212.159.1.105 te3-2.ptn-gw02.plus.net
5 15 ms 212.159.2.124 vl55.ptn-lb01.plus.net
6 16 ms 212.159.13.50 cdns02.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 16 ms 195.166.128.64 lo0-plusnet.pte-ag1.plus.net
3 15 ms 84.92.4.1 ge0-0-0-403.pte-gw1.plus.net
4 16 ms 212.159.0.185 te2-2.pcl-gw01.plus.net
5 16 ms 212.159.2.252 vl63.pcl-lb01.plus.net
6 15 ms 212.159.6.9 cdns01.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 16 ms 195.166.128.64 lo0-plusnet.pte-ag1.plus.net
3 15 ms 84.92.4.2 ge0-0-0-403.pte-gw2.plus.net
4 16 ms 212.159.1.105 te3-2.ptn-gw02.plus.net
5 15 ms 212.159.2.124 vl55.ptn-lb01.plus.net
6 16 ms 212.159.6.10 cdns02.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 16 ms 195.166.128.123 lo0-plusnet.ptn-ag1.plus.net
3 15 ms 84.92.3.9 gi2-2-303.ptn-gw01.plus.net
4 16 ms 212.159.2.124 vl55.ptn-lb01.plus.net
5 16 ms 212.159.13.49 cdns01.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 16 ms 195.166.128.123 lo0-plusnet.ptn-ag1.plus.net
3 16 ms 84.92.3.9 gi2-2-303.ptn-gw01.plus.net
4 15 ms 212.159.2.124 vl55.ptn-lb01.plus.net
5 16 ms 212.159.13.50 cdns02.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 31 ms 195.166.128.123 lo0-plusnet.ptn-ag1.plus.net
3 16 ms 84.92.3.9 gi2-2-303.ptn-gw01.plus.net
4 16 ms 212.159.2.124 vl55.ptn-lb01.plus.net
5 15 ms 212.159.6.9 cdns01.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 31 ms 195.166.128.123 lo0-plusnet.ptn-ag1.plus.net
3 47 ms 84.92.3.9 gi2-2-303.ptn-gw01.plus.net
4 15 ms 212.159.2.124 vl55.ptn-lb01.plus.net
5 16 ms 212.159.6.10 cdns02.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 15 ms 195.166.128.134 lo0-plusnet.pcl-ag04.plus.net
3 16 ms 84.92.0.229 gi1-6-604.pcl-gw02.plus.net
4 16 ms 212.159.2.252 vl63.pcl-lb01.plus.net
5 15 ms 212.159.13.49 cdns01.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 16 ms 195.166.128.134 lo0-plusnet.pcl-ag04.plus.net
3 16 ms 84.92.0.229 gi1-6-604.pcl-gw02.plus.net
4 15 ms 212.159.2.252 vl63.pcl-lb01.plus.net
5 16 ms 212.159.13.50 cdns02.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 47 ms 195.166.128.134 lo0-plusnet.pcl-ag04.plus.net
3 31 ms 84.92.0.229 gi1-6-604.pcl-gw02.plus.net
4 16 ms 212.159.2.252 vl63.pcl-lb01.plus.net
5 31 ms 212.159.6.9 cdns01.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 31 ms 195.166.128.134 lo0-plusnet.pcl-ag04.plus.net
3 16 ms 84.92.0.229 gi1-6-604.pcl-gw02.plus.net
4 31 ms 212.159.2.252 vl63.pcl-lb01.plus.net
5 47 ms 212.159.6.10 cdns02.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 15 ms 195.166.128.72 lo0-plusnet.pte-ag2.plus.net
3 16 ms 84.92.4.89 ge0-0-0-504.pte-gw1.plus.net
4 15 ms 212.159.0.185 te2-2.pcl-gw01.plus.net
5 16 ms 212.159.2.252 vl63.pcl-lb01.plus.net
6 15 ms 212.159.13.49 cdns01.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 47 ms 195.166.128.72 lo0-plusnet.pte-ag2.plus.net
3 31 ms 84.92.4.89 ge0-0-0-504.pte-gw1.plus.net
4 31 ms 212.159.0.185 te2-2.pcl-gw01.plus.net
5 31 ms 212.159.2.252 vl63.pcl-lb01.plus.net
6 47 ms 212.159.13.50 cdns02.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 47 ms 195.166.128.72 lo0-plusnet.pte-ag2.plus.net
3 31 ms 84.92.4.89 ge0-0-0-504.pte-gw1.plus.net
4 31 ms 212.159.0.185 te2-2.pcl-gw01.plus.net
5 16 ms 212.159.2.252 vl63.pcl-lb01.plus.net
6 15 ms 212.159.6.9 cdns01.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 16 ms 195.166.128.72 lo0-plusnet.pte-ag2.plus.net
3 31 ms 84.92.4.89 ge0-0-0-504.pte-gw1.plus.net
4 15 ms 212.159.0.185 te2-2.pcl-gw01.plus.net
5 16 ms 212.159.2.252 vl63.pcl-lb01.plus.net
6 31 ms 212.159.6.10 cdns02.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 16 ms 195.166.128.80 lo0-plusnet.thn-ag3.plus.net
3 93 ms 84.92.3.177 vl303.thn-gw1.plus.net
4 16 ms 212.159.1.53 te3-2.ptn-gw01.plus.net
5 16 ms 212.159.2.124 vl55.ptn-lb01.plus.net
6 31 ms 212.159.13.49 cdns01.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 31 ms 195.166.128.80 lo0-plusnet.thn-ag3.plus.net
3 31 ms 84.92.3.177 vl303.thn-gw1.plus.net
4 172 ms 212.159.1.53 te3-2.ptn-gw01.plus.net
5 16 ms 212.159.2.124 vl55.ptn-lb01.plus.net
6 31 ms 212.159.13.50 cdns02.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 15 ms 195.166.128.80 lo0-plusnet.thn-ag3.plus.net
3 16 ms 84.92.3.177 vl303.thn-gw1.plus.net
4 31 ms 212.159.1.53 te3-2.ptn-gw01.plus.net
5 15 ms 212.159.2.124 vl55.ptn-lb01.plus.net
6 16 ms 212.159.6.9 cdns01.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 31 ms 195.166.128.80 lo0-plusnet.thn-ag3.plus.net
3 16 ms 84.92.3.177 vl303.thn-gw1.plus.net
4 31 ms 212.159.1.53 te3-2.ptn-gw01.plus.net
5 15 ms 212.159.2.124 vl55.ptn-lb01.plus.net
6 16 ms 212.159.6.10 cdns02.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 31 ms 195.166.128.109 lo0-plusnet.pcl-ag03.plus.net
3 94 ms 84.92.0.181 gi1-6-703.pcl-gw01.plus.net
4 16 ms 212.159.2.252 vl63.pcl-lb01.plus.net
5 31 ms 212.159.13.49 cdns01.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 63 ms 195.166.128.109 lo0-plusnet.pcl-ag03.plus.net
3 47 ms 84.92.0.181 gi1-6-703.pcl-gw01.plus.net
4 62 ms 212.159.2.252 vl63.pcl-lb01.plus.net
5 16 ms 212.159.13.50 cdns02.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 31 ms 195.166.128.109 lo0-plusnet.pcl-ag03.plus.net
3 125 ms 84.92.0.181 gi1-6-703.pcl-gw01.plus.net
4 63 ms 212.159.2.252 vl63.pcl-lb01.plus.net
5 47 ms 212.159.6.9 cdns01.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 16 ms 195.166.128.109 lo0-plusnet.pcl-ag03.plus.net
3 15 ms 84.92.0.181 gi1-6-703.pcl-gw01.plus.net
4 16 ms 212.159.2.252 vl63.pcl-lb01.plus.net
5 31 ms 212.159.6.10 cdns02.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 16 ms 195.166.128.53 lo0-plusnet.ptn-ag2.plus.net
3 31 ms 84.92.3.93 gi2-2-204.ptn-gw02.plus.net
4 16 ms 212.159.2.124 vl55.ptn-lb01.plus.net
5 62 ms 212.159.13.49 cdns01.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 32 ms 195.166.128.53 lo0-plusnet.ptn-ag2.plus.net
3 15 ms 84.92.3.93 gi2-2-204.ptn-gw02.plus.net
4 16 ms 212.159.2.124 vl55.ptn-lb01.plus.net
5 16 ms 212.159.13.50 cdns02.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 47 ms 195.166.128.53 lo0-plusnet.ptn-ag2.plus.net
3 31 ms 84.92.3.93 gi2-2-204.ptn-gw02.plus.net
4 15 ms 212.159.2.124 vl55.ptn-lb01.plus.net
5 94 ms 212.159.6.9 cdns01.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 31 ms 195.166.128.53 lo0-plusnet.ptn-ag2.plus.net
3 16 ms 84.92.3.93 gi2-2-204.ptn-gw02.plus.net
4 31 ms 212.159.2.124 vl55.ptn-lb01.plus.net
5 47 ms 212.159.6.10 cdns02.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 16 ms 195.166.128.101 lo0.plusnet.thn-ag1.plus.net
3 16 ms 84.92.4.241 vl703.thn-gw1.plus.net
4 15 ms 212.159.1.53 te3-2.ptn-gw01.plus.net
5 15 ms 212.159.2.124 vl55.ptn-lb01.plus.net
6 16 ms 212.159.13.49 cdns01.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 16 ms 195.166.128.101 lo0.plusnet.thn-ag1.plus.net
3 15 ms 84.92.4.241 vl703.thn-gw1.plus.net
4 16 ms 212.159.1.53 te3-2.ptn-gw01.plus.net
5 31 ms 212.159.2.124 vl55.ptn-lb01.plus.net
6 16 ms 212.159.13.50 cdns02.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 16 ms 195.166.128.101 lo0.plusnet.thn-ag1.plus.net
3 31 ms 84.92.4.241 vl703.thn-gw1.plus.net
4 16 ms 212.159.1.53 te3-2.ptn-gw01.plus.net
5 31 ms 212.159.2.124 vl55.ptn-lb01.plus.net
6 31 ms 212.159.6.9 cdns01.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 16 ms 195.166.128.101 lo0.plusnet.thn-ag1.plus.net
3 15 ms 84.92.4.241 vl703.thn-gw1.plus.net
4 16 ms 212.159.1.53 te3-2.ptn-gw01.plus.net
5 15 ms 212.159.2.124 vl55.ptn-lb01.plus.net
6 16 ms 212.159.6.10 cdns02.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 32 ms 195.166.128.39 lo0-plusnet.pcl-ag02.plus.net
3 16 ms 84.92.0.141 gi1-2-904.pcl-gw02.plus.net
4 16 ms 212.159.2.252 vl63.pcl-lb01.plus.net
5 93 ms 212.159.13.49 cdns01.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 16 ms 195.166.128.39 lo0-plusnet.pcl-ag02.plus.net
3 15 ms 84.92.0.141 gi1-2-904.pcl-gw02.plus.net
4 16 ms 212.159.2.252 vl63.pcl-lb01.plus.net
5 31 ms 212.159.13.50 cdns02.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 15 ms 195.166.128.39 lo0-plusnet.pcl-ag02.plus.net
3 32 ms 84.92.0.141 gi1-2-904.pcl-gw02.plus.net
4 46 ms 212.159.2.252 vl63.pcl-lb01.plus.net
5 32 ms 212.159.6.9 cdns01.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 31 ms 195.166.128.39 lo0-plusnet.pcl-ag02.plus.net
3 32 ms 84.92.0.141 gi1-2-904.pcl-gw02.plus.net
4 15 ms 212.159.2.252 vl63.pcl-lb01.plus.net
5 16 ms 212.159.6.10 cdns02.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 15 ms 195.166.128.27 lo0-plusnet.pcl-ag01.plus.net
3 32 ms 84.92.5.57 gi1-2-803.pcl-gw1.plus.net
4 15 ms 212.159.2.252 vl63.pcl-lb01.plus.net
5 16 ms 212.159.13.49 cdns01.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 15 ms 195.166.128.27 lo0-plusnet.pcl-ag01.plus.net
3 94 ms 84.92.5.57 gi1-2-803.pcl-gw1.plus.net
4 15 ms 212.159.2.252 vl63.pcl-lb01.plus.net
5 32 ms 212.159.13.50 cdns02.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 16 ms 195.166.128.27 lo0-plusnet.pcl-ag01.plus.net
3 16 ms 84.92.5.57 gi1-2-803.pcl-gw1.plus.net
4 31 ms 212.159.2.252 vl63.pcl-lb01.plus.net
5 31 ms 212.159.6.9 cdns01.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 16 ms 195.166.128.27 lo0-plusnet.pcl-ag01.plus.net
3 15 ms 84.92.5.57 gi1-2-803.pcl-gw1.plus.net
4 16 ms 212.159.2.252 vl63.pcl-lb01.plus.net
5 15 ms 212.159.6.10 cdns02.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 15 ms 195.166.128.93 lo0.plusnet.thn-ag2.plus.net
3 31 ms 84.92.4.169 vl604.thn-gw1.plus.net
4 16 ms 212.159.1.53 te3-2.ptn-gw01.plus.net
5 16 ms 212.159.2.124 vl55.ptn-lb01.plus.net
6 16 ms 212.159.13.49 cdns01.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 15 ms 195.166.128.93 lo0.plusnet.thn-ag2.plus.net
3 31 ms 84.92.4.169 vl604.thn-gw1.plus.net
4 16 ms 212.159.1.53 te3-2.ptn-gw01.plus.net
5 47 ms 212.159.2.124 vl55.ptn-lb01.plus.net
6 16 ms 212.159.13.50 cdns02.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 47 ms 195.166.128.93 lo0.plusnet.thn-ag2.plus.net
3 31 ms 84.92.4.169 vl604.thn-gw1.plus.net
4 125 ms 212.159.1.53 te3-2.ptn-gw01.plus.net
5 15 ms 212.159.2.124 vl55.ptn-lb01.plus.net
6 32 ms 212.159.6.9 cdns01.plus.net
1 0 ms 192.168.1.1 Router-adsl
2 31 ms 195.166.128.93 lo0.plusnet.thn-ag2.plus.net
3 47 ms 84.92.4.169 vl604.thn-gw1.plus.net
4 16 ms 212.159.1.53 te3-2.ptn-gw01.plus.net
5 15 ms 212.159.2.124 vl55.ptn-lb01.plus.net
6 16 ms 212.159.6.10 cdns02.plus.net
If anyone can be bothered to check, please post current tracerts to DNS from your particular gateway IF they appear to be different to those detailed above. There's no point whatsoever posting duplicate info and all that, it's only in any way interesting (to me if no one else) if there are any significant differences now.
Good piece of work there Mike - if I get time I'll see if I can make a table of the results which will be easier to refer to. It has raised two three questions in my mind:
1. Given that it's recommended that you have DNS servers over two different subnets, I wonder why all gateways are not configured like pte-ag1 with cdns01 on the nearest site as at present and cdns02 on the other site to give more resilience?
2. Which two DNS IPs are allocated to the router when you connect to each gateway?
3. Are the allocations and routing the same on 21CN?
1. Given that it's recommended that you have DNS servers over two different subnets, I wonder why all gateways are not configured like pte-ag1 with cdns01 on the nearest site as at present and cdns02 on the other site to give more resilience?
2. Which two DNS IPs are allocated to the router when you connect to each gateway?
3. Are the allocations and routing the same on 21CN?
Quote from: Bob The tunneling of the ERX's has changed numerous times over recent months and it would be a nightmare to keep that, and other things, up to date!
[
And I guess that without such documentation - it will be a nightmare to keep maintained?
M
Quote from: Bob Without referring to the problem documentation and knowing what instance you're talking about, I can't really be specific. Having said that there would obvioulsy have been problems for anybody connected to the PCL pipes and OSPF wouldn't have helped there.
Either of the 2 most recent major router outages at PCL would suffice if you think there is any benefit whatsoever in looking at it in more detail. The most recent one that occurred over the Xmas shutdown period would perhaps be the better as that appeared to demonstrate the problem at it's best ... or should I say worst ! ... and it's also the one outage I have most experience of as well. For an unrelated gateway in an unrelated data centre to be fully functional in absolutely all respects apart from the ability to perform DNS look-ups at PN is pretty unforgivable in my view unless there were extenuating circumstances. I have no idea what the problem actually was because service.status reports etc. do not provide that level of detail of course but if the problem was of a serious nature with the DNS load-balancer at PCL for instance then that pretty much means around 50% of customers lost the use of their connection for a very significant period of time if the system wasn't working as intended or unless they had followed the often given advice on here of not using or ever relying on PN DNS servers ! I do not in any way understand about tunnelling etc. so spare me the details but surely, any routing decisions should be made at the gateway that I'm actually connected to shouldn't it ? How the connection got there in the first place or where you route stuff after seems kinda totally irrelevant if you can't make the 'right' decision at the first 'official' point in the chain and all that. If I'm connected to 195.166.128.72 (as I was) and something somewhere along the way was preventing access to 212.159.2.252 (and beyond) then my DNS requests should presumably have been routed to 212.159.2.124 instead by whatever means was available to achieve that connection. A degraded service obviously but at least a service that actually made some effort to work rather than just sitting there not capable of doing anything much at all without user intervention.
i.e. if something like
1 0 ms 192.168.1.1 Router-adsl
2 47 ms 195.166.128.72 lo0-plusnet.pte-ag2.plus.net
3 15 ms 84.92.4.89 ge0-0-0-504.pte-gw1.plus.net
4 16 ms 212.159.0.185 te2-2.pcl-gw01.plus.net
5 * * no response * [should have been 212.159.2.252 vl63.pcl-lb01.plus.net]
6 * * no response * [should have been 212.159.13.49 cdns01.plus.net]
7 * * no response * - - -
...
occurred at any time then
1 0 ms 192.168.1.1 Router-adsl
2 31 ms 195.166.128.72 lo0-plusnet.pte-ag2.plus.net
3 16 ms 84.92.4.89 ge0-0-0-504.pte-gw1.plus.net
4 15 ms 212.159.1.102 te2-4.pte-gw2.plus.net
5 16 ms 212.159.1.105 te3-2.ptn-gw02.plus.net
6 31 ms 212.159.2.124 vl55.ptn-lb01.plus.net
7 16 ms 212.159.13.49 cdns01.plus.net
should have been automatically substituted instead if I correctly understand what you're suggesting should happen. Something like this did not happen at all even after some very considerable period of time had elapsed from the fault first becoming apparent. So plenty of time for a fault situation to have been detected and routing changed accordingly yet still no DNS. The DNS service was conspicuous by it's absence for several hours I seem to recall. I think I could probably quote you exact times if you want but I don't have the relevant stuff to hand in order to look it up at the mo.
Quote There's plenty of other reasons other than routing for a DNS lookup to fail.
Very true ... but just to clarify, I didn't mean the occasional and/or regular but intermittent failed look-up for reason or reasons unknown. I was meaning a particular DNS IP address not responding in any useful way whatsoever for a significant period of time. I would also point out that I didn't intend to imply it was necessarily very recently for that matter either so possibly before any such system was available. However, if I bothered to look for it and relevant data is actually available in my logs, then I'm way more than a bit certain that I could manage to find instances when 212.159.13.49 was 100% unresponsive for a significant period of time and 212.159.13.50 (or some other temporary DNS address I had configured at the time) was being used. Does a server missing, powered down, faulty or otherwise being unresponsive to DNS requests technically constitute a routing failure or not ?
Quote
Quote from: jelv 2. Which two DNS IPs are allocated to the router when you connect to each gateway?
There assigned in pairs, which pair you get depends on which central you connect to I think although all four customer facing VIPs will route to the same place in most circumstances:
212.159.13.49/59, and
212.159.6.9/10
All my tests and historic records appear to indicate that the assigned DNS addresses are 212.159.6.9/10. Historically and on average it appears to be mainly 212.159.6.10 as primary and 212.159.6.9 as secondary although they do get swapped around on occasions for no seemingly obvious reason. The assignment is by no means apparently gateway dependent nor does it appear to be a random selection either. It could perhaps be account name or assigned IP or some other 'internal' thing dependent of course. Either way, I have yet to see 212.159.13.49/50 being assigned at any time EVER ... although I obviously haven't trawled back through every single logfile I have lying around but my archive logs do go back to October 2005 if anyone would like to request a specific date range for me to check for likely DNS assignment around any particular time !!! However, if it's just a 'simple' load-balancer and destination IP is pretty much being ignored just so long as it's one of the 4 expected ones then it's totally irrelevant which are being used isn't it ? All roads (primarily if not always) lead to Rome and all that
EDIT: 212.159.13.49/50 has only ever been assigned to my connection on and prior to 13th Jan 2006 and was always assigned as primary/secondary respectively regardless of gateway. 212.159.6.9/10 has been assigned on every occasion since 20th Jan 2006, regardless of gateway but not consistently as primary/secondary respectively..
Here's just a fairly random sample of log entries extracted for 7 different days around the time I was investigating why things in general apparently weren't working quite as they should be despite there being "no known problems" and all that. Please note that the stupid number of reboots shown below is quite intentional and not in any way indicative of some fault with the connection, the router or indeed anything at all at this end. These were all manual reboots of my router for reasons various.
2009-12-27 23:00:35 Local3.Info 192.168.1.1 Jan 1 00:00:49 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.53; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2009-12-27 23:00:56 Local3.Info 192.168.1.1 Jan 1 00:01:10 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.39; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2009-12-27 23:01:15 Local3.Info 192.168.1.1 Jan 1 00:01:29 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.64; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2009-12-27 23:01:37 Local3.Info 192.168.1.1 Jan 1 00:01:53 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.53; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2009-12-27 23:02:02 Local3.Info 192.168.1.1 Jan 1 00:02:17 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.27; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2009-12-27 23:02:30 Local3.Info 192.168.1.1 Jan 1 00:02:45 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.123; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2009-12-27 23:03:16 Local3.Info 192.168.1.1 Jan 1 00:03:32 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.64; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2009-12-28 04:10:27 Local3.Info 192.168.1.1 Jan 1 00:00:44 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.101; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2009-12-28 04:10:49 Local3.Info 192.168.1.1 Jan 1 00:01:06 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.80; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2009-12-28 04:11:10 Local3.Info 192.168.1.1 Jan 1 00:01:27 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.72; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2009-12-31 10:27:42 Local3.Info 192.168.1.1 Jan 1 00:00:39 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.109; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2009-12-31 10:28:06 Local3.Info 192.168.1.1 Jan 1 00:01:03 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.101; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2009-12-31 10:28:27 Local3.Info 192.168.1.1 Jan 1 00:01:24 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.123; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2009-12-31 10:28:46 Local3.Info 192.168.1.1 Jan 1 00:01:45 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.101; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2009-12-31 10:29:08 Local3.Info 192.168.1.1 Jan 1 00:02:06 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.101; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2009-12-31 10:29:33 Local3.Info 192.168.1.1 Jan 1 00:02:32 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.123; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2009-12-31 10:30:17 Local3.Info 192.168.1.1 Jan 1 00:03:15 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.101; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2009-12-31 12:03:39 Local3.Info 192.168.1.1 Jan 1 00:00:36 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.109; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2009-12-31 12:03:54 Local3.Info 192.168.1.1 Jan 1 00:00:52 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.101; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2009-12-31 12:04:13 Local3.Info 192.168.1.1 Jan 1 00:01:10 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.72; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-01 20:40:36 Local3.Info 192.168.1.1 Jan 1 00:00:54 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.80; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-01 20:40:55 Local3.Info 192.168.1.1 Jan 1 00:01:14 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.101; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-01 20:41:16 Local3.Info 192.168.1.1 Jan 1 00:01:34 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.101; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-01 20:41:31 Local3.Info 192.168.1.1 Jan 1 00:01:50 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.72; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2010-01-03 09:06:53 Local3.Info 192.168.1.1 Jan 1 00:00:38 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.39; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2010-01-03 09:07:14 Local3.Info 192.168.1.1 Jan 1 00:01:00 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.64; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2010-01-03 09:07:36 Local3.Info 192.168.1.1 Jan 1 00:01:24 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.93; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2010-01-03 09:08:00 Local3.Info 192.168.1.1 Jan 1 00:01:48 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.39; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2010-01-03 09:08:22 Local3.Info 192.168.1.1 Jan 1 00:02:10 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.53; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-03 09:08:48 Local3.Info 192.168.1.1 Jan 1 00:02:36 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.64; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2010-01-03 09:09:31 Local3.Info 192.168.1.1 Jan 1 00:03:22 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.101; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2010-01-03 09:10:45 Local3.Info 192.168.1.1 Jan 1 00:04:38 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.123; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2010-01-03 10:59:57 Local3.Info 192.168.1.1 Jan 1 00:00:46 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.80; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2010-01-03 11:00:17 Local3.Info 192.168.1.1 Jan 1 00:01:06 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.109; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-03 11:00:31 Local3.Info 192.168.1.1 Jan 1 00:01:20 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.64; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-03 11:00:49 Local3.Info 192.168.1.1 Jan 1 00:01:38 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.53; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-03 11:01:09 Local3.Info 192.168.1.1 Jan 1 00:01:59 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.80; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-03 11:01:40 Local3.Info 192.168.1.1 Jan 1 00:02:29 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.123; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-03 11:02:22 Local3.Info 192.168.1.1 Jan 1 00:03:14 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.64; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2010-01-03 12:10:16 Local3.Info 192.168.1.1 Jan 1 00:00:38 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.80; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-03 12:10:33 Local3.Info 192.168.1.1 Jan 1 00:00:58 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.123; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-03 12:10:55 Local3.Info 192.168.1.1 Jan 1 00:01:20 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.64; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-03 12:11:13 Local3.Info 192.168.1.1 Jan 1 00:01:38 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.53; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-03 12:11:34 Local3.Info 192.168.1.1 Jan 1 00:01:59 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.123; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-03 12:12:07 Local3.Info 192.168.1.1 Jan 1 00:02:32 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.109; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-03 12:12:47 Local3.Info 192.168.1.1 Jan 1 00:03:15 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.53; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2010-01-03 12:14:00 Local3.Info 192.168.1.1 Jan 1 00:04:29 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.64; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-03 12:16:20 Local3.Info 192.168.1.1 Jan 1 00:06:50 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.123; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-03 12:46:17 Local3.Info 192.168.1.1 Jan 1 00:00:54 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.101; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-03 12:47:02 Local3.Info 192.168.1.1 Jan 1 00:01:42 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.109; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-03 12:47:31 Local3.Info 192.168.1.1 Jan 1 00:02:11 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.101; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-03 12:47:53 Local3.Info 192.168.1.1 Jan 1 00:02:33 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.101; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-03 12:48:21 Local3.Info 192.168.1.1 Jan 1 00:03:03 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.80; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-03 12:49:05 Local3.Info 192.168.1.1 Jan 1 00:03:47 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.80; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2010-01-03 12:50:21 Local3.Info 192.168.1.1 Jan 1 00:05:08 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.93; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-03 12:52:43 Local3.Info 192.168.1.1 Jan 1 00:07:33 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.123; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-03 13:05:23 Local3.Info 192.168.1.1 Jan 1 00:00:43 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.64; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2010-01-03 13:26:17 Local3.Info 192.168.1.1 Jan 1 00:06:22 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.134; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-03 16:19:43 Local3.Info 192.168.1.1 Jan 1 00:00:59 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.101; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2010-01-03 16:20:06 Local3.Info 192.168.1.1 Jan 1 00:01:22 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.72; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-04 20:09:35 Local3.Info 192.168.1.1 Jan 1 00:00:39 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.27; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2010-01-04 20:12:08 Local3.Info 192.168.1.1 Jan 1 00:00:36 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.27; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-04 20:12:28 Local3.Info 192.168.1.1 Jan 1 00:00:56 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.109; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-04 20:58:19 Local3.Info 192.168.1.1 Jan 1 00:00:40 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.53; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-04 20:58:34 Local3.Info 192.168.1.1 Jan 1 00:00:59 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.101; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2010-01-04 20:58:56 Local3.Info 192.168.1.1 Jan 1 00:01:21 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.39; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2010-01-04 20:59:18 Local3.Info 192.168.1.1 Jan 1 00:01:42 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.64; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2010-01-04 20:59:49 Local3.Info 192.168.1.1 Jan 1 00:02:13 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.101; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2010-01-04 21:00:19 Local3.Info 192.168.1.1 Jan 1 00:02:43 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.27; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-04 21:00:58 Local3.Info 192.168.1.1 Jan 1 00:03:25 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.64; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2010-01-04 22:01:28 Local3.Info 192.168.1.1 Jan 1 00:00:50 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.53; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2010-01-04 22:02:04 Local3.Info 192.168.1.1 Jan 1 00:01:26 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.123; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2010-01-04 22:02:27 Local3.Info 192.168.1.1 Jan 1 00:01:48 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.53; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-04 22:02:59 Local3.Info 192.168.1.1 Jan 1 00:02:21 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.64; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-05 01:07:49 Local3.Info 192.168.1.1 Jan 1 00:00:39 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.80; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2010-01-05 01:08:09 Local3.Info 192.168.1.1 Jan 1 00:00:59 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.39; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2010-01-05 01:08:42 Local3.Info 192.168.1.1 Jan 1 00:01:34 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.109; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2010-01-05 09:08:47 Local3.Info 192.168.1.1 Jan 1 00:00:44 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.27; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-05 09:09:08 Local3.Info 192.168.1.1 Jan 1 00:01:08 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.101; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-05 09:09:24 Local3.Info 192.168.1.1 Jan 1 00:01:24 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.80; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-05 09:09:45 Local3.Info 192.168.1.1 Jan 1 00:01:46 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.72; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2010-01-06 10:46:39 Local3.Info 192.168.1.1 Jan 1 00:00:39 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.53; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2010-01-06 10:46:58 Local3.Info 192.168.1.1 Jan 1 00:01:01 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.123; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2010-01-06 10:47:21 Local3.Info 192.168.1.1 Jan 1 00:01:24 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.101; Primary DNS : 212.159.6.9 Secondary DNS : 212.159.6.10
2010-01-06 10:47:39 Local3.Info 192.168.1.1 Jan 1 00:01:42 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.27; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2010-01-06 10:47:55 Local3.Info 192.168.1.1 Jan 1 00:01:59 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.101; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2010-01-06 10:48:23 Local3.Info 192.168.1.1 Jan 1 00:02:27 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.72; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
2010-01-06 19:40:24 Local3.Info 192.168.1.1 Jan 1 00:00:39 Vigor: IPCP Opening (PPPoA); Own IP Address : 212.xxx.yyy.zzz Peer IP Address : 195.166.128.72; Primary DNS : 212.159.6.10 Secondary DNS : 212.159.6.9
I never use the assigned DNS IPs and always have 212.159.13.49/50 configured as primary and secondary respectively. I seem to remember that this is also the PN recommended settings as well ... or at least I think it was the last time I looked anyway.
I tried connecting a number of times recently and found that I was always getting 6.9 and 6.10 (although contrary to Mikes observations I saw them more often on that order rather than reversed).
Following on from Mike's comments and your replies I still think this is a good question that merits an answer:
Following on from Mike's comments and your replies I still think this is a good question that merits an answer:
Quote from: jelv 1. Given that it's recommended that you have DNS servers over two different subnets, I wonder why all gateways are not configured like pte-ag1 with cdns01 on the nearest site as at present and cdns02 on the other site to give more resilience?