Alan DeKok wrote:
mnisay <mnisay@aim-consultants.com> wrote:
before, the assigned DNS IP address are being properly assigned to dialup customers, now that we have changed our IP block addresses, 10% of the dialup customers are still getting the OLD DNS IP addresses, which is wrong.
Is the RADIUS server assigning DNS servers in the old config? If not, it's not a RADIUS problem.
I am assigning the DNS IP from the radius server itself, most of them gets it right, but some of them, new or old customers get the old DNS IPs. I tried flushing their DNS caches and connect their laptops in our network to get the right DNS IP, but when they get back home, they go back to the old wrong way of getting the old DNS IPs. Cisco docs does not say more of flushing DNS caches in the router level except rebooting it.
And there's no standard way to assign DNS servers, either.
I agree with this. I am beginning to think the issue is more of the customer modem types since I was forcing their connection to get the correct new DNS IPs.
i double checked name-servers declaration in the router level , what could it be?
Have searched the mailing list, some have the same experience and ends with no solutions either, they just lessenned the occurences only by forcing DNS assignment from attributes using Ascend attribture. No further clues. :(