Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

DNS Resolution broken #8809

Open
lucaderi opened this issue Nov 9, 2024 · 2 comments
Open

DNS Resolution broken #8809

lucaderi opened this issue Nov 9, 2024 · 2 comments
Labels

Comments

@lucaderi
Copy link
Member

lucaderi commented Nov 9, 2024

image

@lucaderi lucaderi added the Bug label Nov 9, 2024
@MarcoPamio
Copy link

It happens also with our installation.
Our university netwok is a /16 class-B network and sometimes, the resolution of the hosts is with DNS names is wrong.
Some wrong examples:

  • ocsp.digicert.com
  • emupdate.avcdn.net
  • ocsp.comodoca.com
  • ocsp.digicert.com
  • r11.o.lencr.org
  • msedge.b.tlu.dl.delivery.mp.microsoft.com
  • pbs.twimg.com
    image

(they seem to be related to akamai or "certificate traffic")

We are using a SINGLE 10Gbps port to MIRROR (monitor) traffic inside a cisco4500 on a Port-Channel interface (2x10Gbps). I know that it can fail if the sum of the IN/OUT traffic exceedes 10 Gbps, but for now we have less then 2 Gbps max traffic.
I will probably buy another 10Gbps module in the future, to have tx and rx at (maximun) speed.
cisco IOS monitor:

monitor session 1 source interface Po2
monitor session 1 destination interface Te2/2

Let us know if the bug is fixed, thank you.
Marco

@MatteoBiscosi
Copy link
Member

Hi @MarcoPamio we pushed quite a few fixes for this issue, could you please update to the latest dev version and let me know?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants