1072010 - Unable to connect to fs from yvr

Status: VERIFIED FIXED

(Infrastructure & Operations Graveyard :: NetOps: Office Other, task)

Description

[Ralph Giles (:rillian)]

I was trying to reach our internal fileserver today from the YVR office, and was unable to. Browser just spins for a while and times out.

DNS returns an internal ip for 'fs':

$ host fs
fs.corp.yvr1.mozilla.com is an alias for fs.mv.mozilla.com.
fs.mv.mozilla.com has address 10.250.0.34

But I cannot ping that ip, or connect to it over http. mtr suggests the routing is incorrect:

 1. fw1.corp.yvr1.mozilla.net         0.0%     3    0.5   0.5   0.4   0.5   0.0
 2. 64.213.70.193                     0.0%     3    1.0   1.0   1.0   1.1   0.0
 3. ???

i.e. it's routing traffic to a private IP out some global crossing router.

Comment 1

[Dave Curado :dcurado]

Hi,
The IP address that 'fs' is resolving to (10.250.0.34) no longer exists in our network.
That was an IP address used in the Mountain View office at Castro Street.
Looks like whoever was responsible for that server did not remove the old
DNS record. =-(  

For completeness: when the firewall (also your local router) tries to forward 
your traffic, it doesn't have a route for 10.250.x.x, so the firewall sends the
packet out its default route, which is your local Internet connection.
It looks wrong, but it's actually correct.

Sorry, I don't have a clue about the internal file server. 
I'm thing EUS would know?  
It'll be another 4 hours until people on the West Coast are around.
But I will double back at that time and see if I can find out the new name
of this resource.  Will update this bug once I get the story.

Thanks -- Dave

Comment 2

[Ralph Giles (:rillian)]

Thanks for responding. Hopefully we can update the dns record, then. Or delete it if the server no longer exists.

Re default routes, I would have expected we'd have null routes for all private subnets we're not using, rather than relying on an upstream carrier to do the right thing?

Comment 3

[Dave Curado :dcurado]

I just asked #servicedesk about the file server -- hoping to find someone who knows
something.

Yeah, you raise a good point -- I suppose we could add a null route for 10/8 so that
we crater the packets right away... will give it some thought.
Thanks for suggesting it!

Will update this bug when I figure out the last word on that file server.

Comment 4

[Dave Curado :dcurado]

OK, the word I've got back is that the old fs server is "all kinds of dead"

I will remove the dns record, and will also bring up the idea of adding a null
route for 10/8 on our edge routers in the next staff meeting.

Thanks,
Dave

Comment 5

[Ralph Giles (:rillian)]

Thanks!