You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In my company we have a very strict security policy. For the build-machine the firewall is configured to really only allow the IP-addresses, which are really needed for NUGET-restore to work.
These are IP-addresses configured at the moment, which match the DNS A-records of api.nuget.org
13.107.238.60
13.107.237.60
In the past the IP-addresses changed about three times per year. On 2023-02-28 at 21:00 this address was visible only once: 13.107.253.60
But then it switched back to the above addresses.
This causes a lot of pain, because on the build-machine the NUGET restore just gets stuck, which is very frustrating for the developer creating and maintaining his build-pipeline. As there is no error-message indicating that the firewall is blocking the request, it is nearly impossible for the developer to see that the firewall needs to be reconfigured. And as the reconfiguration of the firewall takes places in the IT-department, he has to create an ICT-ticket, which take very long resolve.
My questions are:
Why do the IP-address change from time to time ?
Is the are complete list of IP-addresses, which are going to be used in the future ?
Do the A-records of api.nuget.org depend on the geolocation of the client ?
Is there load-balancing in the place, which cause the IP-addresses to change ?
It seems that trafficmanager.net from Microsoft is used (see nslookup) below. Can someone provide more detailed information about the overall nuget.org infrastructure ?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
In my company we have a very strict security policy. For the build-machine the firewall is configured to really only allow the IP-addresses, which are really needed for NUGET-restore to work.
These are IP-addresses configured at the moment, which match the DNS A-records of api.nuget.org
In the past the IP-addresses changed about three times per year. On 2023-02-28 at 21:00 this address was visible only once: 13.107.253.60
But then it switched back to the above addresses.
This causes a lot of pain, because on the build-machine the NUGET restore just gets stuck, which is very frustrating for the developer creating and maintaining his build-pipeline. As there is no error-message indicating that the firewall is blocking the request, it is nearly impossible for the developer to see that the firewall needs to be reconfigured. And as the reconfiguration of the firewall takes places in the IT-department, he has to create an ICT-ticket, which take very long resolve.
My questions are:
Beta Was this translation helpful? Give feedback.
All reactions